From: "Bhanu Prakash Gollapudi" <bprakash@broadcom.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: "James E.J. Bottomley" <JBottomley@parallels.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] bnx2fc: use kthread_create_on_node
Date: Fri, 29 Jul 2011 12:22:50 -0700 [thread overview]
Message-ID: <4E33088A.80903@broadcom.com> (raw)
In-Reply-To: <1311923178.7845.21.camel@edumazet-laptop>
On 7/29/2011 12:06 AM, Eric Dumazet wrote:
> Since bnx2fc_percpu_thread_create() creates percpu kthread, it makes
> sense to use kthread_create_on_node() to get proper NUMA affinity for
> kthread stack.
>
> Signed-off-by: Eric Dumazet<eric.dumazet@gmail.com>
> CC: "James E.J. Bottomley"<JBottomley@parallels.com>
Thanks Eric.
Acked-by: Bhanu Prakash Gollapudi <bprakash@broadcom.com>
> ---
> drivers/scsi/bnx2fc/bnx2fc_fcoe.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/scsi/bnx2fc/bnx2fc_fcoe.c b/drivers/scsi/bnx2fc/bnx2fc_fcoe.c
> index a97aff3..9843434 100644
> --- a/drivers/scsi/bnx2fc/bnx2fc_fcoe.c
> +++ b/drivers/scsi/bnx2fc/bnx2fc_fcoe.c
> @@ -2161,9 +2161,9 @@ static void bnx2fc_percpu_thread_create(unsigned int cpu)
>
> p =&per_cpu(bnx2fc_percpu, cpu);
>
> - thread = kthread_create(bnx2fc_percpu_io_thread,
> - (void *)p,
> - "bnx2fc_thread/%d", cpu);
> + thread = kthread_create_on_node(bnx2fc_percpu_io_thread,
> + (void *)p, cpu_to_node(cpu),
> + "bnx2fc_thread/%d", cpu);
> /* bind thread to the cpu */
> if (likely(!IS_ERR(p->iothread))) {
> kthread_bind(thread, cpu);
>
>
>
next prev parent reply other threads:[~2011-07-29 19:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 7:06 [PATCH] bnx2fc: use kthread_create_on_node Eric Dumazet
2011-07-29 19:22 ` Bhanu Prakash Gollapudi [this message]
2012-05-30 0:26 ` Bhanu Prakash Gollapudi
2012-05-30 0:33 ` Joe Perches
2012-05-30 8:30 ` James Bottomley
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=4E33088A.80903@broadcom.com \
--to=bprakash@broadcom.com \
--cc=JBottomley@parallels.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.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 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.