linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bruce Fields <bfields@fieldses.org>
To: Jeff Layton <jeff.layton@primarydata.com>
Cc: Trond Myklebust <trond.myklebust@primarydata.com>,
	linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/6] NFS DRC scalability patches
Date: Tue, 5 Aug 2014 16:51:05 -0400	[thread overview]
Message-ID: <20140805205105.GA23341@fieldses.org> (raw)
In-Reply-To: <20140804074546.7c63e725@tlielax.poochiereds.net>

On Mon, Aug 04, 2014 at 07:45:46AM -0400, Jeff Layton wrote:
> On Sun,  3 Aug 2014 13:05:58 -0400
> Trond Myklebust <trond.myklebust@primarydata.com> wrote:
> 
> > Hi Bruce,
> > 
> > The following patchset is again more an FYI than a must have, but it
> > addresses a significant scalability problem for NFSv3 when running
> > over 10GigE and 40GigE networks. At one point, I was seeing >60% CPU
> > spinning on the DRC global spinlock...
> > 
> > The one thing to note is that because the statistics are moved outside
> > spinlocking, then their accuracy is slightly reduced (I do convert the
> > number of entries into an atomic, so that is still 100% correct). The
> > right thing to do there is probably to convert those into per-cpu
> > counters, however I've not had time to do so for now.
> > 
> 
> Consider adding some FIXME comments to that effect? While not terribly
> important, it would be good to fix them at some point.
> 
> > Cheers,
> >   Trond
> > 
> > Trond Myklebust (6):
> >   nfsd: Clean up drc cache in preparation for global spinlock
> >     elimination
> >   nfsd: convert the lru list into a per-bucket thing
> >   nfsd: Remove the cache_hash list
> >   nfsd: convert num_drc_entries to an atomic_t
> >   nfsd: split DRC global spinlock into per-bucket locks
> >   nfsd: Reorder nfsd_cache_match to check more powerful discriminators
> >     first
> > 
> >  fs/nfsd/cache.h    |   1 -
> >  fs/nfsd/nfscache.c | 205 +++++++++++++++++++++++++++++------------------------
> >  2 files changed, 113 insertions(+), 93 deletions(-)
> > 
> 
> Looks good. Nice work! You can add this to each since they all look
> good to me. It would be good to fix up the stats collection and the
> comments, but I wouldn't want to hold up this work for that.
> 
>     Reviewed-by: Jeff Layton <jlayton@primarydata.com>

Could you also rebase this to my for-3.17?  (Or to 3.17-rc1, whenever
that comes out.)  Not urgent, but there appear to be some minor
conflicts.

--b.

      reply	other threads:[~2014-08-05 20:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-03 17:05 [PATCH 0/6] NFS DRC scalability patches Trond Myklebust
2014-08-03 17:05 ` [PATCH 1/6] nfsd: Clean up drc cache in preparation for global spinlock elimination Trond Myklebust
2014-08-03 17:06   ` [PATCH 2/6] nfsd: convert the lru list into a per-bucket thing Trond Myklebust
2014-08-03 17:06     ` [PATCH 3/6] nfsd: Remove the cache_hash list Trond Myklebust
2014-08-03 17:06       ` [PATCH 4/6] nfsd: convert num_drc_entries to an atomic_t Trond Myklebust
2014-08-03 17:06         ` [PATCH 5/6] nfsd: split DRC global spinlock into per-bucket locks Trond Myklebust
2014-08-03 17:06           ` [PATCH 6/6] nfsd: Reorder nfsd_cache_match to check more powerful discriminators first Trond Myklebust
2014-08-04 11:44           ` [PATCH 5/6] nfsd: split DRC global spinlock into per-bucket locks Jeff Layton
2014-08-04 11:45 ` [PATCH 0/6] NFS DRC scalability patches Jeff Layton
2014-08-05 20:51   ` Bruce Fields [this message]

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=20140805205105.GA23341@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=jeff.layton@primarydata.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@primarydata.com \
    /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).