From: NeilBrown <neilb@suse.de>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/2] revised sunrpc deferral patches
Date: Thu, 07 Oct 2010 15:29:46 +1100 [thread overview]
Message-ID: <20101007042637.26629.60300.stgit@localhost.localdomain> (raw)
Hi Bruce,
Here is the incremental clean-up as requested, plus I've fixed the
problem I found with the cache_limit_deferers patch.
I think that'll do for now.
I cannot think of any better way to do what lockd does with
deferrals, so I think we need to keep deferrals after all.
Thanks,
NeilBrown
---
NeilBrown (2):
sunrpc: Simplify cache_defer_req and related functions.
sunrpc/cache: centralise handling of size limit on deferred list.
net/sunrpc/cache.c | 110 +++++++++++++++++++++++++++-------------------------
1 files changed, 58 insertions(+), 52 deletions(-)
--
Signature
next reply other threads:[~2010-10-07 4:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 4:29 NeilBrown [this message]
2010-10-07 4:29 ` [PATCH 1/2] sunrpc: Simplify cache_defer_req and related functions NeilBrown
2010-10-12 0:07 ` J. Bruce Fields
2010-10-07 4:29 ` [PATCH 2/2] sunrpc/cache: centralise handling of size limit on deferred list NeilBrown
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=20101007042637.26629.60300.stgit@localhost.localdomain \
--to=neilb@suse.de \
--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 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).