On Fri, 14 Dec 2007 01:33:45 +0100 Andi Kleen <[email protected]> wrote:
> Kyle McMartin <[email protected]> writes:
>
> > I'd bet, in the __read_mostly case at least, that there's no
> > improvement in almost all cases.
>
> I bet you're wrong. Cache line behaviour is critical, much more
> than pipeline behaviour (which unlikely affects). That is because
> if you eat a cache miss it gets really expensive, which e.g.
> a mispredicted jump is relatively cheap in comparison. We're talking
> one or more orders of magnitude.
So... once we've moved all read-mostly variables into __read_mostly, what
is left behind in bss?
All the write-often variables. All optimally packed together to nicely
maximise cacheline sharing.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
