From: Rusty Russell <rusty@rustcorp.com.au>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH RFC] cpu alloc cleanups and implementation improvement
Date: Mon, 17 Nov 2008 23:53:17 +1030 [thread overview]
Message-ID: <200811172353.18356.rusty@rustcorp.com.au> (raw)
Hi all,
I've argued with Christoph that his implementation contains gratuitous
obsolescence of perfectly-good APIs; hopefully providing real patches will
give us a more useful debate.
It's in easy stages. There are three general cleanup patches, then four
patches to expose the current module percpu allocator as a the general dynamic
percpu allocator, then documentation, a new __get_cpu_ptr() primitive and
finally a test patch.
I hope this adds some light,
Rusty.
next reply other threads:[~2008-11-17 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-17 13:23 Rusty Russell [this message]
2008-11-20 16:35 ` [PATCH RFC] cpu alloc cleanups and implementation improvement Christoph Lameter
2008-11-21 5:31 ` Stephen Rothwell
2008-11-21 14:49 ` Christoph Lameter
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=200811172353.18356.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--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