lkml.org 
[lkml]   [2003]   [May]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: [PATCH] kmalloc_percpu
From
   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/

\
 
 \ /
  Last update: 2005-03-22 13:35    [W:0.368 / U:0.040 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site