From: Eric Dumazet <eric.dumazet@gmail.com>
To: David Rientjes <rientjes@google.com>
Cc: Christoph Lameter <cl@linux.com>,
Eric Dumazet <edumazet@google.com>,
Nishanth Aravamudan <nacc@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
Anton Blanchard <anton@samba.org>,
Andrew Morton <akpm@linux-foundation.org>,
Tejun Heo <tj@kernel.org>, Oleg Nesterov <oleg@redhat.com>,
Jan Kara <jack@suse.cz>, Thomas Gleixner <tglx@linutronix.de>,
Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
linux-mm@kvack.org, Wanpeng Li <liwanp@linux.vnet.ibm.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Ben Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [PATCH] kthread: ensure locality of task_struct allocations
Date: Wed, 29 Jan 2014 22:14:51 -0800 [thread overview]
Message-ID: <1391062491.28432.68.camel@edumazet-glaptop2.roam.corp.google.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1401291622550.22974@chino.kir.corp.google.com>
On Wed, 2014-01-29 at 16:27 -0800, David Rientjes wrote:
> Eric, did you try this when writing 207205a2ba26 ("kthread: NUMA aware
> kthread_create_on_node()") or was it always numa_node_id() from the
> beginning?
Hmm, I think I did not try this, its absolutely possible NUMA_NO_NODE
was better here.
next prev parent reply other threads:[~2014-01-30 6:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 18:38 [PATCH] kthread: ensure locality of task_struct allocations Nishanth Aravamudan
2014-01-29 8:13 ` David Rientjes
2014-01-29 15:58 ` Christoph Lameter
2014-01-30 0:27 ` David Rientjes
2014-01-30 6:14 ` Eric Dumazet [this message]
2014-01-30 22:47 ` David Rientjes
2014-01-30 23:08 ` Nishanth Aravamudan
2014-01-30 23:31 ` David Rientjes
2014-01-31 15:14 ` Christoph Lameter
2014-01-29 15:57 ` Christoph Lameter
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=1391062491.28432.68.camel@edumazet-glaptop2.roam.corp.google.com \
--to=eric.dumazet@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=cl@linux.com \
--cc=edumazet@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liwanp@linux.vnet.ibm.com \
--cc=nacc@linux.vnet.ibm.com \
--cc=oleg@redhat.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=rientjes@google.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.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;
as well as URLs for NNTP newsgroup(s).