From: Tom Haynes <thomas.haynes@primarydata.com>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>,
Anna Schumaker <anna.schumaker@netapp.com>
Subject: [PATCH 0/3] FF_FLAGS_NO_READ_IO
Date: Wed, 18 May 2016 14:07:53 -0700 [thread overview]
Message-ID: <1463605676-82483-1-git-send-email-loghyr@primarydata.com> (raw)
FF_FLAGS_NO_READ_IO is a hint the mds can use to inform the
client that an IOMODE_RW layout segment should not be used
for READ traffic and that the client should instead request
an IOMODE_READ layout segment. This can be used to isolate
only WRITE traffic onto the IOMODE_RW layout segment.
Tom Haynes (3):
nfs/flexfiles: Helper function to detect FF_FLAGS_NO_READ_IO
nfs/flexfiles: Use the layout segment for reading unless it a
IOMODE_RW and reading is disabled
pnfs: pnfs_update_layout needs to consider if strict iomode checking
is on
fs/nfs/filelayout/filelayout.c | 2 ++
fs/nfs/flexfilelayout/flexfilelayout.c | 50 +++++++++++++++++++++++--------
fs/nfs/flexfilelayout/flexfilelayout.h | 10 ++++++-
fs/nfs/flexfilelayout/flexfilelayoutdev.c | 6 ++++
fs/nfs/pnfs.c | 34 +++++++++++++--------
fs/nfs/pnfs.h | 1 +
6 files changed, 77 insertions(+), 26 deletions(-)
--
1.8.3.1
next reply other threads:[~2016-05-18 21:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 21:07 Tom Haynes [this message]
2016-05-18 21:07 ` [PATCH 1/3] nfs/flexfiles: Helper function to detect FF_FLAGS_NO_READ_IO Tom Haynes
2016-05-18 21:07 ` [PATCH 2/3] nfs/flexfiles: Use the layout segment for reading unless it a IOMODE_RW and reading is disabled Tom Haynes
2016-05-18 21:07 ` [PATCH 3/3] pnfs: pnfs_update_layout needs to consider if strict iomode checking is on Tom Haynes
2016-05-24 20:20 ` [PATCH 0/3] FF_FLAGS_NO_READ_IO Anna Schumaker
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=1463605676-82483-1-git-send-email-loghyr@primarydata.com \
--to=thomas.haynes@primarydata.com \
--cc=anna.schumaker@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.com \
/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).