From: Andrew Morton <akpm@linux-foundation.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: eric.dumazet@gmail.com, ak@linux.intel.com, 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:07:56 -0800 [thread overview]
Message-ID: <20110119120756.cd554fb1.akpm@linux-foundation.org> (raw)
In-Reply-To: <1293131522.2170.798.camel@laptop>
On Thu, 23 Dec 2010 20:12:02 +0100
Peter Zijlstra <peterz@infradead.org> wrote:
> On Thu, 2010-12-09 at 16:44 -0800, akpm@linux-foundation.org wrote:
> > +struct task_struct *kthread_create_on_cpu(int (*threadfn)(void *data),
> > + void *data,
> > + int cpu,
> > + const char namefmt[],
> > + ...)
>
> I thought it was agreed that name sucked too much to live?
I agreed ;)
> All other *_on_cpu() interfaces actually do stuff on that cpu, but this
> does not in fact create a cpu affine task.
The patches are stuck in my tree awaiting some movement here..
next prev parent reply other threads:[~2011-01-19 20:08 UTC|newest]
Thread overview: 11+ 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-23 19:12 ` Peter Zijlstra
2010-12-23 21:45 ` Andrew Morton
2011-01-19 20:07 ` Andrew Morton [this message]
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
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=20110119120756.cd554fb1.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 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.