Messages in this thread | | | Date | Mon, 5 May 2003 21:28:16 -0700 | From | Andrew Morton <> | Subject | Re: [PATCH] kmalloc_percpu |
| |
Rusty Russell <rusty@rustcorp.com.au> wrote: > > > I think the fixed size pool is perfectly reasonable. > > Yes. It's a tradeoff. I think it's worth it at the moment (although > I'll add a limited printk to __alloc_percpu if it fails). >
It's OK as long as nobody uses the feature! Once it starts to be commonly used (say, in driver ->open() methods) then we'll get into the same problems as with vmalloc exhaustion, vmalloc fragmentation, large physically-contig allocations, etc.
Ho-hum. Can the magical constant become a __setup thing? - 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/
| |