Generic Linux architectural discussions
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: akpm@linux-foundation.org
Cc: mm-commits@vger.kernel.org, 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: Thu, 23 Dec 2010 20:12:02 +0100	[thread overview]
Message-ID: <1293131522.2170.798.camel@laptop> (raw)
In-Reply-To: <201012100044.oBA0ivp3016990@imap1.linux-foundation.org>

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?

All other *_on_cpu() interfaces actually do stuff on that cpu, but this
does not in fact create a cpu affine task.

  parent reply	other threads:[~2010-12-23 19:12 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 [this message]
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
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=1293131522.2170.798.camel@laptop \
    --to=peterz@infradead.org \
    --cc=ak@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --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=mm-commits@vger.kernel.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