Re: [PATCH UPDATED] percpu: use dynamic percpu allocator as thedefault percpu allocator

[Christoph Lameter]

On Wed, 1 Apr 2009, Ingo Molnar wrote:

> > Yes its better for the variables to be all together if its not on hot
> > cache paths. And its better to keep the __read_mostly segment reserved for
> > frequently accessed variables.
>
> We need __access_rarely i guess.

Better leave as is. __read_mostly is for hot code paths. __read_mostly
should be packed as tightly as possible to increase the chance that one
cacheline includes multiple of the critical variables for the hot code
paths. Too much __read_mostly defeats its purpose.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/