Linux NFS development
 help / color / mirror / Atom feed
From: Trond Myklebust <trondmy@hammerspace.com>
To: "anna@kernel.org" <anna@kernel.org>,
	"bcodding@redhat.com" <bcodding@redhat.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 1/1] NFS: New mount option force_rdirplus
Date: Wed, 12 Mar 2025 22:48:17 +0000	[thread overview]
Message-ID: <ef4218cd2eb30558692857d02ea1518e1e06684f.camel@hammerspace.com> (raw)
In-Reply-To: <4a471ab1bdea1052f45d894c967d0a6b6e38d4a6.1741806879.git.bcodding@redhat.com>

On Wed, 2025-03-12 at 15:46 -0400, Benjamin Coddington wrote:
> There are certain users that wish to force the NFS client to choose
> READDIRPLUS over READDIR for a particular mount.  Add a new kernel
> mount
> option "force_rdirplus" to carry that intent.

Could we perhaps convert rdirplus to be a string with an optional
payload? Does the "fs_param_can_be_empty" flag allow you to convert
rdirplus into something that can behave as currently if you just
specify '-ordirplus', but that would allow you to specify '-
ordirplus=force' if you wanted to always use readdirplus?



-- 
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com



  reply	other threads:[~2025-03-12 22:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-12 19:46 [PATCH 0/1] Mount option - force READDIRPLUS Benjamin Coddington
2025-03-12 19:46 ` [PATCH 1/1] NFS: New mount option force_rdirplus Benjamin Coddington
2025-03-12 22:48   ` Trond Myklebust [this message]
2025-03-12 22:57     ` Benjamin Coddington
2025-03-12 23:03       ` Trond Myklebust
2025-03-13 14:20   ` kernel test robot

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=ef4218cd2eb30558692857d02ea1518e1e06684f.camel@hammerspace.com \
    --to=trondmy@hammerspace.com \
    --cc=anna@kernel.org \
    --cc=bcodding@redhat.com \
    --cc=linux-nfs@vger.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