From: Andi Kleen <ak@suse.de>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: linux-kernel@vger.kernel.org, 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: Re: [discuss] [RFC] NUMA aware kthread_create() ?
Date: Fri, 2 Dec 2005 13:32:08 +0100 [thread overview]
Message-ID: <20051202123208.GA9766@wotan.suse.de> (raw)
In-Reply-To: <439023A3.4090201@cosmosbay.com>
On Fri, Dec 02, 2005 at 11:36:19AM +0100, Eric Dumazet wrote:
> 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 ?
I don't know of plans. Feel free to do it, although I'm not sure
it will help very much because the stack is relatively small.
-Andi
next prev parent reply other threads:[~2005-12-02 12:32 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 ` [RFC] NUMA aware kthread_create() ? Eric Dumazet
2005-12-02 12:32 ` Andi Kleen [this message]
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=20051202123208.GA9766@wotan.suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=dada1@cosmosbay.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome