Messages in this thread | | | Date | Mon, 5 May 2003 01:47:29 -0700 | From | Andrew Morton <> | Subject | Re: [PATCH] kmalloc_percpu |
| |
Rusty Russell <rusty@rustcorp.com.au> wrote: > > This is the kmalloc_percpu patch.
How does it work? What restrictions does it have, and what compromises were made?
+#define PERCPU_POOL_SIZE 32768
What's this?
The current implementation of kmalloc_per_cpu() turned out to be fairly disappointing because of the number of derefs which were necessary to get at the data in fastpaths. How does this implementation compare?
Thanks. - 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/
| |