From: NeilBrown <neilb@suse.de>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/2] NFSD: restrict PF_LESS_THROTTLE to loop-back requests.
Date: Mon, 12 May 2014 11:22:47 +1000 [thread overview]
Message-ID: <20140512012120.20840.68685.stgit@notabene.brown> (raw)
As PF_LESS_THROTTLE now has a slightly broader meaning it makes sense
to restrict it to only the times it is actually needed - when write
requests come from the local host.
Thanks,
NeilBrown
---
NeilBrown (2):
SUNRPC: track whether a request is coming from a loop-back interface.
nfsd: Only set PF_LESS_THROTTLE when really needed.
fs/nfsd/nfssvc.c | 6 ------
fs/nfsd/vfs.c | 12 ++++++++++++
include/linux/sunrpc/svc.h | 1 +
include/linux/sunrpc/svc_xprt.h | 1 +
net/sunrpc/sunrpc.h | 13 +++++++++++++
net/sunrpc/svcsock.c | 5 +++++
6 files changed, 32 insertions(+), 6 deletions(-)
--
Signature
next reply other threads:[~2014-05-12 1:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 1:22 NeilBrown [this message]
2014-05-12 1:22 ` [PATCH 1/2] SUNRPC: track whether a request is coming from a loop-back interface NeilBrown
2014-05-12 1:22 ` [PATCH 2/2] nfsd: Only set PF_LESS_THROTTLE when really needed NeilBrown
2014-05-22 19:59 ` [PATCH 0/2] NFSD: restrict PF_LESS_THROTTLE to loop-back requests 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=20140512012120.20840.68685.stgit@notabene.brown \
--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).