From: Trond Myklebust <trondmy@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
Anna Schumaker <anna@kernel.org>
Subject: [PATCH v5 0/3] Initial NFS client support for RWF_DONTCACHE
Date: Tue, 9 Sep 2025 21:53:41 -0400 [thread overview]
Message-ID: <cover.1757177140.git.trond.myklebust@hammerspace.com> (raw)
In-Reply-To: <cover.1755612705.git.trond.myklebust@hammerspace.com>
From: Trond Myklebust <trond.myklebust@hammerspace.com>
The main issue is allowing support on 2 stage writes (i.e. unstable
WRITE followed by a COMMIT) since those don't follow the current
assumption that the 'dropbehind' flag can be fulfilled as soon as the
writeback lock is dropped.
v2:
- Make use of the new iocb parameter for nfs_write_begin()
v3:
- Set/clear PG_DROPBEHIND on the head of the nfs_page group
- Simplify helper folio_end_dropbehind
v4:
- Replace filemap_end_dropbehind_write() with folio_end_dropbehind()
- Add a helper to replace folio_end_writeback with an equivalent that
does not attempt to interpret the dropbehind flag
- Keep the folio dropbehind flag set until the NFS client is ready to
call folio_end_dropbehind.
- Don't try to do a read-modify-write in nfs_write_begin() if the folio
has the dropbehind flag set.
v5:
- Change helper function export types to EXPORT_SYMBOL_GPL
Trond Myklebust (3):
filemap: Add a helper for filesystems implementing dropbehind
filemap: Add a version of folio_end_writeback that ignores dropbehind
NFS: Enable use of the RWF_DONTCACHE flag on the NFS client
fs/nfs/file.c | 9 +++++----
fs/nfs/nfs4file.c | 1 +
fs/nfs/write.c | 4 +++-
include/linux/pagemap.h | 2 ++
mm/filemap.c | 34 ++++++++++++++++++++++++++--------
5 files changed, 37 insertions(+), 13 deletions(-)
--
2.51.0
next parent reply other threads:[~2025-09-10 1:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1755612705.git.trond.myklebust@hammerspace.com>
2025-09-10 1:53 ` Trond Myklebust [this message]
2025-09-10 1:53 ` [PATCH v5 1/3] filemap: Add a helper for filesystems implementing dropbehind Trond Myklebust
2025-09-10 1:53 ` [PATCH v5 2/3] filemap: Add a version of folio_end_writeback that ignores dropbehind Trond Myklebust
2025-09-10 1:53 ` [PATCH v5 3/3] NFS: Enable use of the RWF_DONTCACHE flag on the NFS client Trond Myklebust
2025-09-10 1:59 ` [PATCH v5 0/3] Initial NFS client support for RWF_DONTCACHE 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=cover.1757177140.git.trond.myklebust@hammerspace.com \
--to=trondmy@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anna@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.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