From: Dipankar Sarma <dipankar@gamebox.net>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org,
Rusty Russell <rusty@rustcorp.com.au>,
Ravikiran G Thirumalai <kiran@in.ibm.com>
Subject: Re: [patch] kmalloc_percpu -- 2 of 2
Date: Fri, 6 Dec 2002 02:53:07 +0530 [thread overview]
Message-ID: <20021206025307.A20657@dikhow> (raw)
In-Reply-To: <3DEFB0EB.9893DB9@digeo.com>; from akpm@digeo.com on Thu, Dec 05, 2002 at 09:10:16PM +0100
On Thu, Dec 05, 2002 at 09:10:16PM +0100, Andrew Morton wrote:
>
> I'd suggest that you drop the new allocator until a compelling
> need for it (in real, live 2.5/2.6 code) has been demonstrated.
Fine with me since atleast one workaround for fragmentation with small
allocations is known. I can't see anything in 2.5 timeframe
requiring small per-cpu allocations.
Would you like me to resubmit a simple kmalloc-only version ?
Thanks
Dipankar
next prev parent reply other threads:[~2002-12-05 21:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-04 12:12 [patch] kmalloc_percpu -- 1 of 2 Ravikiran G Thirumalai
2002-12-04 12:15 ` [patch] kmalloc_percpu -- 2 " Ravikiran G Thirumalai
2002-12-04 19:34 ` Andrew Morton
2002-12-05 3:42 ` Dipankar Sarma
2002-12-05 4:32 ` Andrew Morton
2002-12-05 4:47 ` William Lee Irwin III
2002-12-05 10:53 ` Dipankar Sarma
2002-12-05 11:23 ` yodaiken
2002-12-05 11:28 ` William Lee Irwin III
2002-12-05 12:41 ` Dipankar Sarma
2002-12-05 15:08 ` yodaiken
2002-12-05 20:02 ` Andrew Morton
2002-12-05 21:23 ` Dipankar Sarma [this message]
2002-12-05 22:15 ` Andrew Morton
2002-12-09 5:30 ` Ravikiran G Thirumalai
2002-12-09 5:57 ` Andrew Morton
2002-12-09 19:28 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021206025307.A20657@dikhow \
--to=dipankar@gamebox.net \
--cc=akpm@digeo.com \
--cc=kiran@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).