From: Jeff Layton <jlayton@redhat.com>
To: bfields@fieldses.org
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH v2 0/3] nfsd: better stats gathering for DRC
Date: Fri, 15 Feb 2013 12:23:07 -0500 [thread overview]
Message-ID: <1360948990-2265-1-git-send-email-jlayton@redhat.com> (raw)
This is a respin of the series I posted yesterday. The main differences are:
1/ I dropped the first patch that fixes the comments, since Bruce said
that he was applying it.
2/ I've changed the csum_misses counter to only increment when the
checksum comparison fails (instead of checksum and the length). I
also cleaned up the comparator function a bit.
3/ I added a new patch to track memory utilization by the DRC, figuring
that might be handy if someone runs into memory problems later.
Further comments and suggestions welcome. I'd like to see this in 3.9
if possible.
Jeff Layton (3):
nfsd: break out comparator into separate function
nfsd: track memory utilization in the DRC
nfsd: add new reply_cache_stats file in nfsdfs
fs/nfsd/cache.h | 1 +
fs/nfsd/nfscache.c | 77 +++++++++++++++++++++++++++++++++++++++++++++---------
fs/nfsd/nfsctl.c | 9 +++++++
3 files changed, 74 insertions(+), 13 deletions(-)
--
1.7.11.7
next reply other threads:[~2013-02-15 17:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 17:23 Jeff Layton [this message]
2013-02-15 17:23 ` [PATCH v2 1/3] nfsd: break out comparator into separate function Jeff Layton
2013-02-15 17:23 ` [PATCH v2 2/3] nfsd: track memory utilization in the DRC Jeff Layton
2013-02-15 17:23 ` [PATCH v2 3/3] nfsd: add new reply_cache_stats file in nfsdfs Jeff Layton
2013-02-15 17:29 ` Chuck Lever
2013-02-15 18:34 ` Jeff Layton
2013-02-15 20:04 ` [PATCH RFC] nfsd: report length of the largest hash chain in reply cache stats Jeff Layton
2013-02-15 21:14 ` Chuck Lever
2013-02-15 22:20 ` Jeff Layton
2013-02-16 13:39 ` J. Bruce Fields
2013-02-16 17:18 ` Chuck Lever
2013-02-17 16:00 ` J. Bruce Fields
2013-02-17 19:58 ` Chuck Lever
2013-02-18 14:21 ` Jeff Layton
2013-02-18 14:30 ` J. Bruce Fields
2013-02-18 14:39 ` Jeff Layton
2013-02-18 16:18 ` Chuck Lever
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=1360948990-2265-1-git-send-email-jlayton@redhat.com \
--to=jlayton@redhat.com \
--cc=bfields@fieldses.org \
--cc=linux-nfs@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.