From: Greg Banks <gnb@fastmail.fm>
To: NeilBrown <neilb@suse.de>
Cc: linux-nfs@vger.kernel.org, David Miller <davem@davemloft.net>,
linux-kernel <linux-kernel@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: Fw: [PATCH] sunrpc: use better NUMA affinities
Date: Fri, 29 Jul 2011 16:05:40 +1000 [thread overview]
Message-ID: <4E324DB4.7060600@fastmail.fm> (raw)
In-Reply-To: <20110729153207.17af3085@notabene.brown>
On 29/07/11 15:32, NeilBrown wrote:
>
> Hi Greg,
> I saw this patch float past and thought of you... You may not be interested
> any more, and it may be a perfectly good patch that does not need any
> comment, but I thought I would let you know anyway.
Thanks Neil.
I've trimmed the cc list to limit the number of copies Trond and Bruce get:)
> From: Eric Dumazet<eric.dumazet@gmail.com>
> To: Trond Myklebust<Trond.Myklebust@netapp.com>
> Cc: "J. Bruce Fields"<bfields@fieldses.org>, Neil Brown<neilb@suse.de>,
> David Miller<davem@davemloft.net>, linux-nfs@vger.kernel.org, netdev
> <netdev@vger.kernel.org>, linux-kernel<linux-kernel@vger.kernel.org>
> Subject: [PATCH] sunrpc: use better NUMA affinities
>
>
> Use NUMA aware allocations to reduce latencies and increase throughput.
Briefly looking at the patch, it doesn't seem wrong but I'm surprised
it's (still) necessary.
Some years ago at SGI we encountered that same problem; we solved it by
delaying all the allocation of data structures associated with a thread
so that they were performed in the thread itself, after the thread had
been limited to run on a certain set of CPUs. Thus the thread's normal
allocation behaviour resulted in all of it's allocations being from
node-local pages. It was a pretty ugly patch, but it worked and made a
huge difference to NFS throughput on large NUMA boxes.
Later Jeff Layton converted the sunrpc svc startup code to use kthreads
and at the time I read his patches, pointed out this problem, and posted
my patch for comparison
http://linux-nfs.org/pipermail/nfsv4/2008-May/008760.html
I seem to remember coming to the conclusion that Jeff eventually
addressed this problem...am I misremembering or did something regress?
--
Greg.
next parent reply other threads:[~2011-07-29 6:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110729153207.17af3085@notabene.brown>
2011-07-29 6:05 ` Greg Banks [this message]
[not found] ` <4E324DB4.7060600-97jfqw80gc6171pxa8y+qA@public.gmane.org>
2011-07-29 6:30 ` Fw: [PATCH] sunrpc: use better NUMA affinities 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
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
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=4E324DB4.7060600@fastmail.fm \
--to=gnb@fastmail.fm \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--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).