Messages in this thread | | | Date | Mon, 05 May 2003 22:57:48 -0700 (PDT) | Subject | Re: [PATCH] kmalloc_percpu | From | "David S. Miller" <> |
| |
From: Andrew Morton <akpm@digeo.com> Date: Mon, 5 May 2003 23:55:49 -0700
How about we leave kmalloc_per_cpu as-is (it uses kmalloc()), and only apply Rusty's new code to DEFINE_PER_CPU?
I propose to make it use kmalloc() all the time.
It simply doesn't make sense to use a pool given what you've shown me. If we've decided that any limit whatsover is bad, why impose any limit at all? Smells like bad design frankly.
Normal DEFINE_PER_CPU() need not a pool, therefore we don't need a pool for anything.
Make kmalloc_per_cpu() merely a convenience macro, made up of existing non-percpu primitives. - 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/
| |