Messages in this thread | | | Date | Mon, 5 May 2003 18:52:48 -0700 | From | Andrew Morton <> | Subject | Re: [PATCH] kmalloc_percpu |
| |
Rusty Russell <rusty@rustcorp.com.au> wrote: > > > +#define PERCPU_POOL_SIZE 32768 > > > > What's this? > > OK. It has a size restriction: PERCPU_POOL_SIZE is the maximum total > kmalloc_percpu + static DECLARE_PER_CPU you'll get, ever. This is the > main downside. It's allocated at boot.
And is subject to fragmentation.
Is it not possible to go allocate another N * PERCPU_POOL_SIZE from slab if it runs out?
That way, PERCPU_POOL_SIZE only needs to be sized for non-modular static percpu data, which sounds more robust.
- 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/
| |