All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@kernel.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Jeff Layton <jlayton@kernel.org>, NeilBrown <neil@brown.name>,
	Olga Kornievskaia <okorniev@redhat.com>,
	Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
	Trond Myklebust <trondmy@kernel.org>,
	Anna Schumaker <anna@kernel.org>,
	linux-nfs@vger.kernel.org, linus-fsdevel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [RFC PATCH v2 6/8] NFSD: add io_cache_read controls to debugfs interface
Date: Mon, 14 Jul 2025 12:47:37 -0400	[thread overview]
Message-ID: <aHU0qcrxvmcp0hom@kernel.org> (raw)
In-Reply-To: <6a05d14f-dbf6-4786-ba08-c57f8f4c64e6@oracle.com>

On Thu, Jul 10, 2025 at 06:46:37PM -0400, Chuck Lever wrote:
> On 7/10/25 10:06 AM, Jeff Layton wrote:
> > On Tue, 2025-07-08 at 12:06 -0400, Mike Snitzer wrote:
> >> Add 'io_cache_read' to NFSD's debugfs interface so that: Any data
> >> read by NFSD will either be:
> >> - cached using page cache (NFSD_IO_BUFFERED=0)
> >> - cached but removed from the page cache upon completion
> >>   (NFSD_IO_DONTCACHE=1).
> >> - not cached (NFSD_IO_DIRECT=2)
> >>
> >> io_cache_read is 0 by default.  It may be set by writing to:
> >>   /sys/kernel/debug/nfsd/io_cache_read
> >>
> >> If NFSD_IO_DONTCACHE is specified using 1, FOP_DONTCACHE must be
> >> advertised as supported by the underlying filesystem (e.g. XFS),
> >> otherwise all IO flagged with RWF_DONTCACHE will fail with
> >> -EOPNOTSUPP.
> >>
> >> If NFSD_IO_DIRECT is specified using 2, the IO must be aligned
> >> relative to the underlying block device's logical_block_size. Also the
> >> memory buffer used to store the read must be aligned relative to the
> >> underlying block device's dma_alignment.
> >>
> >> Signed-off-by: Mike Snitzer <snitzer@kernel.org>
> >> ---
> >>  fs/nfsd/debugfs.c | 53 +++++++++++++++++++++++++++++++++++++++++++++++
> >>  fs/nfsd/nfsd.h    |  8 +++++++
> >>  fs/nfsd/vfs.c     | 15 ++++++++++++++
> >>  3 files changed, 76 insertions(+)
> >>
> >> diff --git a/fs/nfsd/debugfs.c b/fs/nfsd/debugfs.c
> >> index 84b0c8b559dc..709646af797a 100644
> >> --- a/fs/nfsd/debugfs.c
> >> +++ b/fs/nfsd/debugfs.c
> >> @@ -27,11 +27,61 @@ static int nfsd_dsr_get(void *data, u64 *val)
> >>  static int nfsd_dsr_set(void *data, u64 val)
> >>  {
> >>  	nfsd_disable_splice_read = (val > 0) ? true : false;
> >> +	if (!nfsd_disable_splice_read) {
> >> +		/*
> >> +		 * Cannot use NFSD_IO_DONTCACHE or NFSD_IO_DIRECT
> >> +		 * if splice_read is enabled.
> >> +		 */
> >> +		nfsd_io_cache_read = NFSD_IO_BUFFERED;
> >> +	}
> >>  	return 0;
> >>  }
> >>  
> >>  DEFINE_DEBUGFS_ATTRIBUTE(nfsd_dsr_fops, nfsd_dsr_get, nfsd_dsr_set, "%llu\n");
> >>  
> >> +/*
> >> + * /sys/kernel/debug/nfsd/io_cache_read
> >> + *
> >> + * Contents:
> >> + *   %0: NFS READ will use buffered IO (default)
> >> + *   %1: NFS READ will use dontcache (buffered IO w/ dropbehind)
> >> + *   %2: NFS READ will use direct IO
> >> + *
> >> + * The default value of this setting is zero (buffered IO is
> >> + * used). This setting takes immediate effect for all NFS
> >> + * versions, all exports, and in all NFSD net namespaces.
> >> + */
> >> +
> > 
> > Could we switch this to use a string instead? Maybe
> > buffered/dontcache/direct ?
> 
> That thought occurred to me too, since it would make the API a little
> more self-documenting, and might be a harbinger of what a future
> export option might look like.
> 
> 
> >> +static int nfsd_io_cache_read_get(void *data, u64 *val)
> >> +{
> >> +	*val = nfsd_io_cache_read;
> >> +	return 0;
> >> +}
> >> +
> >> +static int nfsd_io_cache_read_set(void *data, u64 val)
> >> +{
> >> +	switch (val) {
> >> +	case NFSD_IO_DONTCACHE:
> >> +	case NFSD_IO_DIRECT:
> >> +		/*
> >> +		 * Must disable splice_read when enabling
> >> +		 * NFSD_IO_DONTCACHE or NFSD_IO_DIRECT.
> >> +		 */
> >> +		nfsd_disable_splice_read = true;
> >> +		nfsd_io_cache_read = val;
> >> +		break;
> >> +	case NFSD_IO_BUFFERED:
> >> +	default:
> >> +		nfsd_io_cache_read = NFSD_IO_BUFFERED;
> >> +		break;
> > 
> > I think the default case should leave nfsd_io_cache_read alone and
> > return an error. If we add new values later, and someone tries to use
> > them on an old kernel, it's better to make that attempt error out.
> > 
> > Ditto for the write side controls.
> 
> +1 on both accounts.

I started to implement this just now (so that I can kick v3 of this
patchset out of the nest today) but soon found that debugfs doesn't
provide string-based interface controls.

See simple_attr_open() (which is used by DEFINE_DEBUGFS_ATTRIBUTE).
It only allows u64 to be set/get.

I'll fix the default case to return an error for now though.

Once we graduate from debugfs to a proper per-export control we can
impose string controls/mapping, e.g.:

+static u64 nfsd_io_cache_string_to_mode(const char *nfsd_io_cache_string)
+{
+       u64 val = NFSD_IO_UNKNOWN;
+
+       if (!strncmp(nfsd_io_cache_string, NFSD_IO_BUFFERED_string,
+                    strlen(NFSD_IO_BUFFERED_string)))
+               val = NFSD_IO_BUFFERED;
+       else if (!strncmp(nfsd_io_cache_string, NFSD_IO_DONTCACHE_string,
+                         strlen(NFSD_IO_DONTCACHE_string)))
+               val = NFSD_IO_DONTCACHE;
+       else if (!strncmp(nfsd_io_cache_string, NFSD_IO_DIRECT_string,
+                         strlen(NFSD_IO_DIRECT_string)))
+               val = NFSD_IO_DIRECT;
+
+       return val;
+}
+
+static const char *
+nfsd_io_cache_mode_to_string(const char *nfsd_io_cache_string)
+{
+       char *nfsd_io_cache_string;
+
+       switch (val) {
+       case NFSD_IO_BUFFERED:
+               nfsd_io_cache_string = NFSD_IO_BUFFERED_string;
+               break;
+       case NFSD_IO_DONTCACHE:
+               nfsd_io_cache_string = NFSD_IO_DONTCACHE_string;
+               break;
+       case NFSD_IO_DIRECT:
+               nfsd_io_cache_string = NFSD_IO_DIRECT_string;
+               break;
+       case NFSD_IO_UNKNOWN:
+               nfsd_io_cache_string = NFSD_IO_UNKNOWN_string;
+               break;
+       }
+
+       return nfsd_io_cache_string;
+}

  reply	other threads:[~2025-07-14 16:47 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-08 16:06 [RFC PATCH v2 0/8] NFSD: support DIO Mike Snitzer
2025-07-08 16:06 ` [RFC PATCH v2 1/8] NFSD: Relocate the fh_want_write() and fh_drop_write() helpers Mike Snitzer
2025-07-10 13:59   ` Jeff Layton
2025-07-08 16:06 ` [RFC PATCH v2 2/8] NFSD: Move the fh_getattr() helper Mike Snitzer
2025-07-10 13:59   ` Jeff Layton
2025-07-08 16:06 ` [RFC PATCH v2 3/8] NFSD: filecache: add STATX_DIOALIGN and STATX_DIO_READ_ALIGN support Mike Snitzer
2025-07-10  7:45   ` Christoph Hellwig
2025-07-14 17:46     ` Mike Snitzer
2025-07-08 16:06 ` [RFC PATCH v2 4/8] lib/iov_iter: remove piecewise bvec length checking in iov_iter_aligned_bvec Mike Snitzer
2025-07-10  7:24   ` Christoph Hellwig
2025-07-10  7:32     ` Mike Snitzer
2025-07-10  7:44       ` Christoph Hellwig
2025-07-10 13:52   ` Jeff Layton
2025-07-10 14:48     ` Keith Busch
2025-07-10 16:12       ` Mike Snitzer
2025-07-10 16:29         ` Keith Busch
2025-07-10 17:22           ` Mike Snitzer
2025-07-10 19:51             ` Keith Busch
2025-07-10 19:57             ` Keith Busch
2025-08-01 15:23         ` Keith Busch
2025-08-01 16:10           ` Mike Snitzer
2025-07-08 16:06 ` [RFC PATCH v2 5/8] NFSD: pass nfsd_file to nfsd_iter_read() Mike Snitzer
2025-07-08 16:06 ` [RFC PATCH v2 6/8] NFSD: add io_cache_read controls to debugfs interface Mike Snitzer
2025-07-10  7:47   ` Christoph Hellwig
2025-07-14 17:33     ` Mike Snitzer
2025-07-10 14:06   ` Jeff Layton
2025-07-10 22:46     ` Chuck Lever
2025-07-14 16:47       ` Mike Snitzer [this message]
2025-07-15 11:57         ` Jeff Layton
2025-07-08 16:06 ` [RFC PATCH v2 7/8] NFSD: add io_cache_write " Mike Snitzer
2025-07-08 16:06 ` [RFC PATCH v2 8/8] NFSD: issue READs using O_DIRECT even if IO is misaligned Mike Snitzer
2025-07-08 21:22   ` Mike Snitzer
2025-07-10  7:51   ` 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=aHU0qcrxvmcp0hom@kernel.org \
    --to=snitzer@kernel.org \
    --cc=Dai.Ngo@oracle.com \
    --cc=anna@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=jlayton@kernel.org \
    --cc=linus-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neil@brown.name \
    --cc=okorniev@redhat.com \
    --cc=tom@talpey.com \
    --cc=trondmy@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.