From: Christoph Lameter <cl@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH RFC] cpu alloc cleanups and implementation improvement
Date: Fri, 21 Nov 2008 08:49:29 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.64.0811210842580.24965@quilx.com> (raw)
In-Reply-To: <20081121163111.7107315e.sfr@canb.auug.org.au>
On Fri, 21 Nov 2008, Stephen Rothwell wrote:
> > I would not mind if you would take over from here.
>
> So, should I remove the cpu_alloc tree from linux-next?
I think the cpu_alloc branch itself is fine because it only contains the
allocator and a single use case. The only point of disagreement at this
point is the uppercase / lowercase use. Currently its a separate API (its
not replacing allocpercpu) and therefore easy to merge.
The more invasive stuff is stage2 and the following which is not in next
yet. The way I envision to go forward is with a gradual transition to the
new APIs converting dynamic percpu users to use the new percpu operations
and functionality.
The whole thing becomes riskier if we directly replace all allocpercpu
users as proposed by Rusty.
Rusty, are you going to take this on?
next prev parent reply other threads:[~2008-11-21 14:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-17 13:23 Rusty Russell
2008-11-20 16:35 ` Christoph Lameter
2008-11-21 5:31 ` Stephen Rothwell
2008-11-21 14:49 ` Christoph Lameter [this message]
2008-11-22 4:41 ` Rusty Russell
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=Pine.LNX.4.64.0811210842580.24965@quilx.com \
--to=cl@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=sfr@canb.auug.org.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
all inboxes | Powered by JetHome®