From: Trond Myklebust <trondmy@hammerspace.com>
To: "snitzer@kernel.org" <snitzer@kernel.org>,
"jlayton@kernel.org" <jlayton@kernel.org>,
"chuck.lever@oracle.com" <chuck.lever@oracle.com>
Cc: "okorniev@redhat.com" <okorniev@redhat.com>,
"tom@talpey.com" <tom@talpey.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"Dai.Ngo@oracle.com" <Dai.Ngo@oracle.com>,
"neilb@suse.de" <neilb@suse.de>,
"axboe@kernel.dk" <axboe@kernel.dk>
Subject: Re: nfsd: add the ability to enable use of RWF_DONTCACHE for all nfsd IO
Date: Fri, 21 Feb 2025 19:18:21 +0000 [thread overview]
Message-ID: <4351756085f94489329c6065d7eeff22f5079d0d.camel@hammerspace.com> (raw)
In-Reply-To: <42400116f9098ec7f5acc70c2450dd52a2bf8f21.camel@kernel.org>
On Fri, 2025-02-21 at 13:42 -0500, Jeff Layton wrote:
>
> All that said, I don't object to some sort of mechanism to turn this
> on
> more globally, particularly since that would allow us to use this
> with
> v3 I/O as well.
Personally, I think an export option would give the most flexibility.
That would allow the sysadmin to, for instance, put a set of libraries
+ executables that are shared by all clients on one volume which is
exported in the normal fashion. Then putting files that are typically
just accessed by a single client, or that are too huge to fit in cache
memory on a separate volume that could be exported with the new option
set.
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next prev parent reply other threads:[~2025-02-21 19:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 17:12 [PATCH] nfsd: add the ability to enable use of RWF_DONTCACHE for all nfsd IO Mike Snitzer
2025-02-20 18:17 ` Chuck Lever
2025-02-21 15:02 ` Mike Snitzer
2025-02-21 15:25 ` Jeff Layton
2025-02-21 15:36 ` Mike Snitzer
2025-02-21 15:42 ` Jeff Layton
2025-02-21 15:46 ` Chuck Lever
2025-02-21 16:13 ` Trond Myklebust
2025-02-21 18:42 ` Jeff Layton
2025-02-21 19:18 ` Trond Myklebust [this message]
2025-02-21 15:39 ` Chuck Lever
2025-02-21 15:46 ` Jeff Layton
2025-02-21 15:50 ` Chuck Lever
2025-02-20 19:00 ` [PATCH] " Jeff Layton
2025-02-20 19:15 ` Chuck Lever
2025-02-21 15:25 ` Mike Snitzer
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=4351756085f94489329c6065d7eeff22f5079d0d.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=Dai.Ngo@oracle.com \
--cc=axboe@kernel.dk \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=okorniev@redhat.com \
--cc=snitzer@kernel.org \
--cc=tom@talpey.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