From: Andrew Morton <akpm@linux-foundation.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Andi Kleen <ak@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
davem@davemloft.net, dhowells@redhat.com, fenghua.yu@intel.com,
linux-arch@vger.kernel.org, rusty@rustcorp.com.au, tj@kernel.org,
tony.luck@intel.com
Subject: Re: + kthread-numa-aware-kthread_create_on_cpu.patch added to -mm tree
Date: Wed, 19 Jan 2011 12:44:11 -0800 [thread overview]
Message-ID: <20110119124411.864d9d97.akpm@linux-foundation.org> (raw)
In-Reply-To: <1295468515.2653.4.camel@edumazet-laptop>
On Wed, 19 Jan 2011 21:21:55 +0100
Eric Dumazet <eric.dumazet@gmail.com> wrote:
> Le mercredi 19 janvier 2011 __ 12:17 -0800, Andi Kleen a __crit :
> > >
> > > I wont discuss about a function _name_ Andrew.
> > >
> > > If nobody can chose one better than the one I chosed, what can I do ?
> >
> > kthread_create_node() would seem logical (with a node parameter)
> >
> > -Andi
>
> I already explained why I dont like this suggestion.
>
> 1) My plan was to later add cpu affinity.
That would be called kthread_create_on_cpu() except whoops, this patch
already took that.
> 2) All users I converted want to create one kthread per cpu, not per
> node.
kswapd is a potential user. It would want one kthread per node.
next prev parent reply other threads:[~2011-01-19 20:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 0:44 + kthread-numa-aware-kthread_create_on_cpu.patch added to -mm tree akpm
2010-12-10 0:44 ` akpm
2010-12-23 19:12 ` Peter Zijlstra
2010-12-23 21:45 ` Andrew Morton
2011-01-19 20:07 ` Andrew Morton
2011-01-19 20:15 ` Eric Dumazet
2011-01-19 20:17 ` Andi Kleen
2011-01-19 20:21 ` Eric Dumazet
2011-01-19 20:44 ` Andrew Morton [this message]
2011-01-19 20:50 ` Eric Dumazet
2011-01-19 20:59 ` Andrew Morton
2011-01-19 21:10 ` Eric Dumazet
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=20110119124411.864d9d97.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ak@linux.intel.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=eric.dumazet@gmail.com \
--cc=fenghua.yu@intel.com \
--cc=linux-arch@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rusty@rustcorp.com.au \
--cc=tj@kernel.org \
--cc=tony.luck@intel.com \
/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).