* Hua Zhong <[email protected]> wrote:
> We are just trading accuracy for speed here.
no, we are trading _both_ accuracy and speed here! a global 'likeliness'
pointer for commonly executed codepaths is causing global cacheline
ping-pongs - which is as bad as it gets.
the right approach, which incidentally would also be perfectly accurate,
is to store an alloc_percpu()-ed pointer at the call site, not the
counter itself.
the current code needs more work before it can go upstream i think.
Ingo
-
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]
