Rusty Russell <rusty@rustcorp.com.au> wrote:>> This is the kmalloc_percpu patch.

How does it work? What restrictions does it have, andwhat compromises were made?

+#define PERCPU_POOL_SIZE 32768

What's this?

The current implementation of kmalloc_per_cpu() turned out to be fairlydisappointing because of the number of derefs which were necessary to get atthe data in fastpaths. How does this implementation compare?