From: Kazuo Ito <ito_kazuo_g3@lab.ntt.co.jp>
To: "Trond Myklebust" <trond.myklebust@hammerspace.com>,
anna.schumaker@netapp.com, linux-nfs@vger.kernel.org,
konishi.ryusuke@lab.ntt.co.jp,
OS渡辺 <watanabe.hiroyuki@lab.ntt.co.jp>
Subject: [PATCH v2 0/2] pNFS block/SCSI layouts read-modify-write fix&improvement
Date: Thu, 14 Feb 2019 18:34:57 +0900 [thread overview]
Message-ID: <92b9e2a4-8880-3fc6-1f6a-e5ab85ed96e6@lab.ntt.co.jp> (raw)
This set of patches attempt to fix potential data integrity problem
in nfs_want_read_modify_write() and improve full page overwrite
performance of pNFS block/SCSI layouts.
The patch set comprises of two patches:
- 1/2 "pNFS: Fix potential corruption of page being written"
fixes the integrity issue
- 2/2 "pNFS: Avoid read/modify/write when it is not necessary"
addresses the cases where read/modify/write was requested for a full-
page write.
v1 -> v2:
- added the fix for missing PagePrivate in the pNFS block layout
- made the check for full page write a separate inline function
- merged the duplicated code for the pNFS block/SCSI layouts and
for the other layout + normal NFS
- type usage clean up (int to bool, unsigned to unsigned int)
kazuo ito (2):
pNFS: Fix potential corruption of page being written
pNFS: Avoid read/modify/write when it is not necessary
fs/nfs/file.c | 40 ++++++++++++++++++++++++++--------------
1 file changed, 26 insertions(+), 14 deletions(-)
--
2.20.1
next reply other threads:[~2019-02-14 9:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 9:34 Kazuo Ito [this message]
2019-02-21 22:33 ` [PATCH v2 0/2] pNFS block/SCSI layouts read-modify-write fix&improvement 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=92b9e2a4-8880-3fc6-1f6a-e5ab85ed96e6@lab.ntt.co.jp \
--to=ito_kazuo_g3@lab.ntt.co.jp \
--cc=anna.schumaker@netapp.com \
--cc=konishi.ryusuke@lab.ntt.co.jp \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@hammerspace.com \
--cc=watanabe.hiroyuki@lab.ntt.co.jp \
/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).