From: bfields@fieldses.org (J. Bruce Fields)
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Chuck Lever <chuck.lever@oracle.com>
Subject: [GIT PULL] nfsd changes for 5.4
Date: Fri, 27 Sep 2019 16:08:38 -0400 [thread overview]
Message-ID: <20190927200838.GA2618@fieldses.org> (raw)
Please pull nfsd changes from:
git://linux-nfs.org/~bfields/linux.git tags/nfsd-5.4
--b.
----------------------------------------------------------------
Highlights:
- add a new knfsd file cache, so that we don't have to open and
close on each (NFSv2/v3) READ or WRITE. This can speed up
read and write in some cases. It also replaces our readahead
cache.
- Prevent silent data loss on write errors, by treating write
errors like server reboots for the purposes of write caching,
thus forcing clients to resend their writes.
- Tweak the code that allocates sessions to be more forgiving,
so that NFSv4.1 mounts are less likely to hang when a server
already has a lot of clients.
- Eliminate an arbitrary limit on NFSv4 ACL sizes; they should
now be limited only by the backend filesystem and the
maximum RPC size.
- Allow the server to enforce use of the correct kerberos
credentials when a client reclaims state after a reboot.
And some miscellaneous smaller bugfixes and cleanup.
----------------------------------------------------------------
Dave Wysochanski (1):
SUNRPC: Track writers of the 'channel' file to improve cache_listeners_exist
include/linux/sunrpc/cache.h | 6 +++---
net/sunrpc/cache.c | 12 ++++++++----
2 files changed, 11 insertions(+), 7 deletions(-)
next reply other threads:[~2019-09-27 20:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 20:08 J. Bruce Fields [this message]
2019-09-27 22:44 ` [GIT PULL] nfsd changes for 5.4 Linus Torvalds
2019-09-27 23:55 ` J. Bruce Fields
2019-09-28 1:15 ` pr-tracker-bot
2019-09-28 1:15 ` pr-tracker-bot
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=20190927200838.GA2618@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=torvalds@linux-foundation.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