linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trond Myklebust <trondmy@kernel.org>
To: Anna Schumaker <anna@kernel.org>
Cc: linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	Mike Snitzer <snitzer@kernel.org>
Subject: [PATCH v3 0/2] Initial NFS client support for RWF_DONTCACHE
Date: Mon, 18 Aug 2025 07:39:48 -0700	[thread overview]
Message-ID: <cover.1755527537.git.trond.myklebust@hammerspace.com> (raw)

From: Trond Myklebust <trond.myklebust@hammerspace.com>

The following patch set attempts to add support for the RWF_DONTCACHE
flag in preadv2() and pwritev2() on NFS filesystems.

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

Trond Myklebust (2):
  filemap: Add a helper for filesystems implementing dropbehind
  NFS: Enable the RWF_DONTCACHE flag for the NFS client

 fs/nfs/file.c            |  6 ++----
 fs/nfs/nfs4file.c        |  1 +
 fs/nfs/write.c           | 20 +++++++++++++++++---
 include/linux/nfs_page.h |  1 +
 include/linux/pagemap.h  |  1 +
 mm/filemap.c             | 11 +++++++++++
 6 files changed, 33 insertions(+), 7 deletions(-)

-- 
2.50.1


             reply	other threads:[~2025-08-18 14:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-18 14:39 Trond Myklebust [this message]
2025-08-18 14:39 ` [PATCH v3 1/2] filemap: Add a helper for filesystems implementing dropbehind Trond Myklebust
2025-08-18 14:51   ` Matthew Wilcox
2025-08-18 15:59     ` Trond Myklebust
2025-08-18 16:08       ` Matthew Wilcox
2025-08-18 14:39 ` [PATCH v3 2/2] NFS: Enable the RWF_DONTCACHE flag for the NFS client Trond Myklebust
2025-08-18 15:21   ` Matthew Wilcox
2025-08-18 15:56     ` Trond Myklebust
2025-08-18 15:58       ` Matthew Wilcox
2025-08-18 16:49         ` Trond Myklebust
2025-08-18 17:04           ` Matthew Wilcox

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.1755527537.git.trond.myklebust@hammerspace.com \
    --to=trondmy@kernel.org \
    --cc=anna@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=snitzer@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).