From: Mike Snitzer <snitzer@kernel.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Matthew Wilcox <willy@infradead.org>,
trondmy@kernel.org, linux-nfs@vger.kernel.org,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC PATCH 0/3] Initial NFS client support for RWF_DONTCACHE
Date: Thu, 24 Apr 2025 12:51:12 -0400 [thread overview]
Message-ID: <aApsAAYJMMRtKr8h@kernel.org> (raw)
In-Reply-To: <97033bd0-dcf9-4049-8e44-060b7e854952@oracle.com>
On Wed, Apr 23, 2025 at 11:30:21AM -0400, Chuck Lever wrote:
> On 4/23/25 11:22 AM, Matthew Wilcox wrote:
> > On Wed, Apr 23, 2025 at 10:38:37AM -0400, Chuck Lever wrote:
> >> On 4/23/25 12:25 AM, trondmy@kernel.org wrote:
> >>> 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.
> >>
> >> Hi Trond-
> >>
> >> "RFC" in the subject field noted.
> >>
> >> The cover letter does not explain why one would want this facility, nor
> >> does it quantify the performance implications.
> >>
> >> I can understand not wanting to cache on an NFS server, but don't you
> >> want to maintain a data cache as close to applications as possible?
> >
> > If you look at the original work for RWF_DONTCACHE, you'll see this is
> > the application providing the hint that it's doing a streaming access.
> > It's only applied to folios which are created as a result of this
> > access, and other accesses to these folios while the folios are in use
> > clear the flag. So it's kind of like O_DIRECT access, except that it
> > does go through the page cache so there's none of this funky alignment
> > requirement on the userspace buffers.
>
> OK, was wondering whether this behavior was opt-in; sounds like it is.
> Thanks for setting me straight.
Yes, its certainly opt-in (requires setting a flag for each use).
Jens added support in fio relatively recently, see:
https://git.kernel.dk/cgit/fio/commit/?id=43c67b9f3a8808274bc1e0a3b7b70c56bb8a007f
Looking ahead relative to NFSD, as you know we've discussed exposing
per-export config controls to enable use of DONTCACHE. Finer controls
(e.g. only large sequential IO) would be more desirable but I'm not
aware of a simple means to detect such workloads with NFSD.
Could it be that we'd do well to carry through large folio support in
NFSD and expose a configurable threshold that if met or exceeded then
DONTCACHE used?
What is the status of large folio support in NFSD? Is anyone actively
working on it?
Thanks,
Mike
next prev parent reply other threads:[~2025-04-24 16:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 4:25 [RFC PATCH 0/3] Initial NFS client support for RWF_DONTCACHE trondmy
2025-04-23 4:25 ` [RFC PATCH 1/3] filemap: Add a helper for filesystems implementing dropbehind trondmy
2025-04-24 21:30 ` Mike Snitzer
2025-04-23 4:25 ` [RFC PATCH 2/3] filemap: Mark folios as dropbehind in generic_perform_write() trondmy
2025-04-24 21:30 ` Mike Snitzer
2025-04-23 4:25 ` [RFC PATCH 3/3] NFS: Enable the RWF_DONTCACHE flag for the NFS client trondmy
2025-04-24 21:31 ` Mike Snitzer
2025-04-23 14:38 ` [RFC PATCH 0/3] Initial NFS client support for RWF_DONTCACHE Chuck Lever
2025-04-23 15:22 ` Matthew Wilcox
2025-04-23 15:30 ` Chuck Lever
2025-04-24 16:51 ` Mike Snitzer [this message]
2025-04-24 16:59 ` Chuck Lever
2025-04-24 21:29 ` [PATCH 4/3] NFS: add RWF_DONTCACHE support to LOCALIO Mike Snitzer
2025-07-14 6:22 ` [RFC PATCH 0/3] Initial NFS client support for RWF_DONTCACHE Christoph Hellwig
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=aApsAAYJMMRtKr8h@kernel.org \
--to=snitzer@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@kernel.org \
--cc=willy@infradead.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