From: "J. Bruce Fields" <bfields@fieldses.org>
To: Greg Banks <gnb@fastmail.fm>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
Christoph Hellwig <hch@infradead.org>, NeilBrown <neilb@suse.de>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
David Miller <davem@davemloft.net>,
linux-kernel <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] sunrpc: use better NUMA affinities
Date: Fri, 29 Jul 2011 12:48:36 -0400 [thread overview]
Message-ID: <20110729164836.GL23194@fieldses.org> (raw)
In-Reply-To: <F67B6E82-9FA8-464E-B3FB-DC0D4EC18BB0@fastmail.fm>
On Fri, Jul 29, 2011 at 11:30:05PM +1000, Greg Banks wrote:
>
>
> Sent from my iPhone
>
> On 29/07/2011, at 22:11, Eric Dumazet <eric.dumazet@gmail.com> wrote:
>
> > Le vendredi 29 juillet 2011 à 21:58 +1000, Greg Banks a écrit :
> >
> >>
> >> Sure, and a whole lot of the callsites are ("..._%d", cpu), hence the
> >> unfortune :(
> >
> > BTW, we could name nfsd threads differently :
> >
> > Currently, they all are named : "nfsd"
> >
> > If SVC_POOL_PERCPU is selected, we could name them :
> > nfsd_c0 -> nfsd_cN
> >
> > If SVC_POOL_PERNODE is selected, we could name them :
> > nfsd_n0 -> nfsd_nN
> >
> > That would help to check with "ps aux" which cpu/nodes are under
> > stress.
> >
> >
>
> I like it!
Yup, patch welcomed.--b.
next prev parent reply other threads:[~2011-07-29 16:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110729153207.17af3085@notabene.brown>
2011-07-29 6:05 ` Fw: [PATCH] sunrpc: use better NUMA affinities Greg Banks
[not found] ` <4E324DB4.7060600-97jfqw80gc6171pxa8y+qA@public.gmane.org>
2011-07-29 6:30 ` Eric Dumazet
2011-07-29 6:53 ` Greg Banks
[not found] ` <4E3258E1.6020000-97jfqw80gc6171pxa8y+qA@public.gmane.org>
2011-07-29 10:36 ` Christoph Hellwig
2011-07-29 11:58 ` Greg Banks
2011-07-29 12:11 ` Eric Dumazet
2011-07-29 13:30 ` Greg Banks
2011-07-29 16:48 ` J. Bruce Fields [this message]
2011-07-29 16:53 ` J. Bruce Fields
[not found] ` <20110729165345.GM23194-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2011-07-29 18:15 ` Eric Dumazet
2011-07-29 20:34 ` Greg Banks
[not found] ` <F562C6F4-3FC2-4952-A903-8E87E9EF2D9D-97jfqw80gc6171pxa8y+qA@public.gmane.org>
2011-07-29 23:30 ` NeilBrown
[not found] ` <20110730093025.716f3f50-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2011-07-29 23:48 ` J. Bruce Fields
[not found] ` <20110729234857.GA30941-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2011-07-30 4:08 ` Eric Dumazet
2011-07-30 6:06 ` NeilBrown
2011-07-30 6:23 ` Eric Dumazet
2011-07-31 6:58 ` Eric Dumazet
2011-08-27 0:02 ` J. Bruce Fields
[not found] ` <20110827000219.GF18699-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2011-08-28 10:02 ` Eric Dumazet
2011-08-02 1:06 ` J. Bruce Fields
2011-07-29 16:45 ` Fw: " J. Bruce Fields
2011-07-29 20:24 ` Greg Banks
2011-07-29 16:48 ` Fw: " J. Bruce Fields
2011-07-28 18:04 Eric Dumazet
2011-07-29 16:42 ` J. Bruce Fields
[not found] ` <20110729164214.GI23194-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2011-07-29 18:02 ` Eric Dumazet
2011-07-29 18:08 ` J. Bruce Fields
2011-07-29 20:39 ` Greg Banks
2011-08-05 21:28 ` J. Bruce Fields
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=20110729164836.GL23194@fieldses.org \
--to=bfields@fieldses.org \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=gnb@fastmail.fm \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=netdev@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 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).