From: Trond Myklebust <trond.myklebust@primarydata.com>
To: linux-nfs@vger.kernel.org
Subject: [PATCH 0/6] More layoutreturn nits
Date: Fri, 22 Jul 2016 15:33:52 -0400 [thread overview]
Message-ID: <1469216038-71882-1-git-send-email-trond.myklebust@primarydata.com> (raw)
Various non-critical bugfixes and cleanups targeting layoutreturn.
Trond Myklebust (6):
pNFS: Clear the layout return tracking on layout reinitialisation
pNFS: Ensure layoutreturn acts as a completion for layout callbacks
pNFS: Do not set plh_return_seq for non-callback related layoutreturns
pNFS: Remove redundant stateid invalidation
NFS: pnfs_mark_matching_lsegs_return() should match the layout
sequence id
pNFS: Cleanup - don't open code pnfs_mark_layout_stateid_invalid()
fs/nfs/nfs42proc.c | 3 +-
fs/nfs/nfs4proc.c | 3 +-
fs/nfs/pnfs.c | 108 +++++++++++++++++++++++++++++++++--------------------
fs/nfs/pnfs.h | 2 +
4 files changed, 71 insertions(+), 45 deletions(-)
--
2.7.4
next reply other threads:[~2016-07-22 19:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 19:33 Trond Myklebust [this message]
2016-07-22 19:33 ` [PATCH 1/6] pNFS: Clear the layout return tracking on layout reinitialisation Trond Myklebust
2016-07-22 19:33 ` [PATCH 2/6] pNFS: Ensure layoutreturn acts as a completion for layout callbacks Trond Myklebust
2016-07-22 19:33 ` [PATCH 3/6] pNFS: Do not set plh_return_seq for non-callback related layoutreturns Trond Myklebust
2016-07-22 19:33 ` [PATCH 4/6] pNFS: Remove redundant stateid invalidation Trond Myklebust
2016-07-22 19:33 ` [PATCH 5/6] NFS: pnfs_mark_matching_lsegs_return() should match the layout sequence id Trond Myklebust
2016-07-22 19:33 ` [PATCH 6/6] pNFS: Cleanup - don't open code pnfs_mark_layout_stateid_invalid() Trond Myklebust
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=1469216038-71882-1-git-send-email-trond.myklebust@primarydata.com \
--to=trond.myklebust@primarydata.com \
--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).