From: Rusty Russell <rusty@rustcorp.com.au>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
catalin.marinas@arm.com, akpm@linux-foundation.org,
Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [RFC] cpualloc: improvements to per-cpu allocation
Date: Thu, 1 Jan 2009 13:42:58 +1030 [thread overview]
Message-ID: <200901011342.58933.rusty@rustcorp.com.au> (raw)
In-Reply-To: <Pine.LNX.4.64.0812311902050.24421@quilx.com>
On Thursday 01 January 2009 11:33:00 Christoph Lameter wrote:
> On Thu, 1 Jan 2009, Rusty Russell wrote:
>
> > I don't think it's a problem. You still can't use them directly (this
> > wording was not meant to imply that), but you can now hand their addresses
> > to per_cpu_ptr() etc. So zero-based x86-64 should Just Work.
>
> Ok so this is going to be merged for 2.6.29? Its a good cleanup and a step
> forward to our goals.
I'm on the fence, but you've convinced me. I'll put this in linux-next,
and if there's no damage, I'll push to Linus. The actual conversions I'll
send via the maintainers though.
These patches have been around for a while, and though they've been polished
a little more in the last week or so the changes were mainly cosmetic.
Thanks,
Rusty.
prev parent reply other threads:[~2009-01-01 3:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 23:08 [RFC] cpualloc: improvements to per-cpu allocation Rusty Russell
2008-12-30 23:08 ` Rusty Russell
2008-12-31 23:27 ` Christoph Lameter
2009-01-01 0:26 ` Rusty Russell
2009-01-01 1:03 ` Christoph Lameter
2009-01-01 3:12 ` Rusty Russell [this message]
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=200901011342.58933.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=cl@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.