Date: Tue, 6 May 2003 00:22:29 -0700
From: Andrew Morton <akpm@digeo.com>
To: "David S. Miller" <davem@redhat.com>
Cc: rusty@rustcorp.com.au, dipankar@in.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kmalloc_percpu
Message-Id: <20030506002229.631a642a.akpm@digeo.com>
In-Reply-To: <20030505.225748.35026531.davem@redhat.com>
References: <20030505224815.07e5240c.akpm@digeo.com>
	<20030505.223554.88485673.davem@redhat.com>
	<20030505235549.5df75866.akpm@digeo.com>
	<20030505.225748.35026531.davem@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 820
Lines: 23

"David S. Miller" <davem@redhat.com> wrote:
>
> Make kmalloc_per_cpu() merely a convenience macro, made up of existing
> non-percpu primitives.

I think we're agreeing here.

The current kmalloc_percpu() is a wrapper around kmalloc.  That seems OK to
me.

What we _do_ want to solve is the problem that DEFINE_PERCPU() does not work
in modules.  Rusty's patch (reworked to not alter kmalloc_percpu) would suit
that requirement.


(kiran has a new version of kmalloc_percpu() which may be faster than the
current one, but for the purposes of this discussion it's equivalent).

-
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/