Messages in this thread | | | Date | Fri, 27 Jan 2006 16:40:27 -0800 | From | Ravikiran G Thirumalai <> | Subject | Re: [patch 3/4] net: Percpufy frequently used variables -- proto.sockets_allocated |
| |
On Sat, Jan 28, 2006 at 12:21:07AM +0100, Eric Dumazet wrote: > Ravikiran G Thirumalai a écrit : > >On Fri, Jan 27, 2006 at 11:30:23PM +0100, Eric Dumazet wrote: > > Why not use a boot time allocated percpu area (as done today in > setup_per_cpu_areas()), but instead of reserving extra space for module's > percpu data, being able to serve alloc_percpu() from this reserved area (ie > no kmalloced data anymore), and keeping your
At that time ia64 placed a limit on the max size of per-CPU area (PERCPU_ENOUGH_ROOM). I think that the limit is still there, But hopefully 64K per-CPU should be enough for static + dynamic + modules?
Let me do a allyesconfig on my box and verify.
Thanks, Kiran - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |