All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <dada1@cosmosbay.com>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@osdl.org>,
	Ravikiran G Thirumalai <kiran@scalex86.org>,
	ak@suse.de, discuss@x86-64.org, shai@scalex86.org,
	rusty@rustcorp.com.au
Subject: [RFC] NUMA aware kthread_create() ?
Date: Fri, 02 Dec 2005 11:36:19 +0100	[thread overview]
Message-ID: <439023A3.4090201@cosmosbay.com> (raw)
In-Reply-To: <20051202010548.4da3d1bb.akpm@osdl.org>

Hi

Is there any plans about making a kthread_create_on_cpu() version of 
kthread_create(), so that memory allocated for thread stack/info is allocated 
on the node of the target CPU ?

There is a mention about kthread_create_on_cpu() in a comment in 
include/linux/kthread.h, but no implementation.

The current use pattern is

p = kthread_create(ksoftirqd, hcpu, "ksoftirqd/%d", hotcpu);
if (IS_ERR(p)) { error ... }
kthread_bind(p, hotcpu);

So the thread memory is currently allocated on the node of the current cpu, ie 
not the target cpu (hotcpu in this example)

Thank you
Eric Dumazet

  reply	other threads:[~2005-12-02 10:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-02  8:10 [patch 1/3] x86_64: Node local PDA -- early cpu_to_node Ravikiran G Thirumalai
2005-12-02  8:16 ` [patch 2/3] x86_64: Node local PDA -- Use macros to access cpu_pda Ravikiran G Thirumalai
2005-12-02  8:23 ` [patch 3/3] x86_64: Node local PDA -- allocate node local memory for pda Ravikiran G Thirumalai
2005-12-02  8:54   ` Eric Dumazet
2005-12-02 18:24     ` [discuss] " Ravikiran G Thirumalai
2005-12-02  9:05   ` Andrew Morton
2005-12-02 10:36     ` Eric Dumazet [this message]
2005-12-02 12:32       ` [discuss] [RFC] NUMA aware kthread_create() ? Andi Kleen
2005-12-02 11:47   ` [patch 3/3] x86_64: Node local PDA -- allocate node local memory for pda Andi Kleen
2005-12-02 20:02     ` Ravikiran G Thirumalai
2005-12-02 22:41       ` Andi Kleen
2005-12-02 11:43 ` [patch 1/3] x86_64: Node local PDA -- early cpu_to_node Andi Kleen
2005-12-02 22:51   ` [discuss] " Ravikiran G Thirumalai
2005-12-02 23:02     ` Andi Kleen
2005-12-02 23:43       ` Ravikiran G Thirumalai
2005-12-02 23:48         ` Andi Kleen

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=439023A3.4090201@cosmosbay.com \
    --to=dada1@cosmosbay.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=discuss@x86-64.org \
    --cc=kiran@scalex86.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=shai@scalex86.org \
    /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.