Re: [PATCH UPDATED] percpu: use dynamic percpu allocator as the default percpu allocator

Christoph Lameter
2009-04-02T03:34:13Z

On Thu, 2 Apr 2009, Ingo Molnar wrote:

> You didnt really answer to my suggestion(s) though. You only stated
> that:
>
> "problem XYZ is something normal that comes with the cpu caching
> schemes. As long as there is no significant impact on
> performance weare fine with it."
>
> Which i'd proffer is true for any given value of XYZ ;-)

Nope. If XYZ is a significant performance issue then we are not fine with
XYZ. __read_mostly was introduced to deal with signficant false aliasing
issues.

False aliasing can be set to occur anytime you place two variables in the
same cacheline. That is by design in the current cacheline schemes. One
would not place a variable in a separate cacheline without good
reason.