From: Rusty Russell <rusty@rustcorp•com.au>
To: Christoph Lameter <cl@linux-foundation•org>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>, linux-next@vger•kernel.org
Subject: Re: linux-next: cpu_alloc tree
Date: Wed, 17 Dec 2008 22:36:19 +1030 [thread overview]
Message-ID: <200812172236.20226.rusty@rustcorp.com.au> (raw)
In-Reply-To: <Pine.LNX.4.64.0812160851080.18671@quilx.com>
On Wednesday 17 December 2008 01:21:26 Christoph Lameter wrote:
> On Tue, 16 Dec 2008, Stephen Rothwell wrote:
>
> > The cpu_alloc tree has not been included in linux-next since Nov 21. Have
> > your discussions with Rusty come to any conclusions? Should I remove
> > this tree permanently or will it be updated?
>
> I thought Rusty would be doing something. If not then I will bring things
> up to snuff.
Thanks for the prod, I was distracted by cpumasks and local_t, the latter
tangentially related.
The current patches work, but introduce new limits on eg. number of
network devices. Those have to be diverted to a lesser percpu allocator
until we get dynamic percpu sizing. I do not want to block this work on
that: you've shown how useful even small allocs can be in key places.
Expect another set of patches this week.
Thanks,
Rusty.
prev parent reply other threads:[~2008-12-17 12:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 6:05 linux-next: cpu_alloc tree Stephen Rothwell
2008-12-16 14:51 ` Christoph Lameter
2008-12-17 12:06 ` 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=200812172236.20226.rusty@rustcorp.com.au \
--to=rusty@rustcorp$(echo .)com.au \
--cc=cl@linux-foundation$(echo .)org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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