From: Jeff Layton <jlayton@kernel.org>
To: Steve Dickson <steved@redhat.com>, Chuck Lever <cel@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>,
Mike Snitzer <snitzer@kernel.org>
Cc: linux-nfs@vger.kernel.org, Jeff Layton <jlayton@kernel.org>
Subject: [PATCH nfs-utils v2 0/4] exports: add support for new read_io= and write_io= export options
Date: Thu, 29 Oct 2026 08:10:07 -0400 [thread overview]
Message-ID: <20261029-master-v2-0-32bfc6ac16da@kernel.org> (raw)
This is the companion patch series to [1]. Chuck suggested we change the
export options to read_io= and write_io=. That's the only real change
in this version.
The last patch in this adds a new nfsd-iomode-advisor script that
watches various stats on the server and advises the admin what mode to
use.
I consider the advisor optional as it was largely vibe-coded. I'm not
sure I'd trust its advice that far, but it's probably better than
guessing. I did test it on a range of different machine types and it
seemed to do the right thing.
[1]: https://lore.kernel.org/linux-nfs/20261029-export-iomode-v2-6-fe8ec6251a36@kernel.org/
Signed-off-by: Jeff Layton <jlayton@kernel.org>
---
Changes in v2:
- Rename riomode=/wiomode= to read_io=/write_io= to match the kernel series.
- Link to v1: https://lore.kernel.org/r/20261027-master-v1-0-6f1f7a35a83b@kernel.org
---
Jeff Layton (4):
exportfs/mountd/exportd: track the svc_export policy highest attribute
exports: Add read_io= and write_io= export options
exportfs: Display and document read_io= and write_io=
nfsd-iomode-advisor: recommend read_io= and write_io= for an export
configure.ac | 3 +-
support/export/cache.c | 59 +-
support/export/export_policy.c | 29 +-
support/export/v4root.c | 2 +
support/include/exportfs.h | 3 +
support/include/nfsd_netlink.h | 12 +
support/include/nfslib.h | 14 +
support/nfs/exports.c | 51 +
tools/Makefile.am | 2 +-
tools/nfsd-iomode-advisor/Makefile.am | 14 +
tools/nfsd-iomode-advisor/nfsd-iomode-advisor.man | 232 ++++
tools/nfsd-iomode-advisor/nfsd-iomode-advisor.py | 1198 +++++++++++++++++++++
utils/exportfs/exportfs.c | 34 +
utils/exportfs/exports.man | 22 +
14 files changed, 1671 insertions(+), 4 deletions(-)
---
base-commit: 0ed4324cbbb8020039d338d597c1422a980f7085
change-id: 20261014-master-b5afd69e3772
Best regards,
--
Jeff Layton <jlayton@kernel.org>
next reply other threads:[~2026-10-29 12:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 12:10 Jeff Layton [this message]
2026-10-29 12:10 ` [PATCH nfs-utils v2 1/4] exportfs/mountd/exportd: track the svc_export policy highest attribute Jeff Layton
2026-10-29 12:10 ` [PATCH nfs-utils v2 2/4] exports: Add read_io= and write_io= export options Jeff Layton
2026-10-29 12:10 ` [PATCH nfs-utils v2 3/4] exportfs: Display and document read_io= and write_io= Jeff Layton
2026-10-29 12:10 ` [PATCH nfs-utils v2 4/4] nfsd-iomode-advisor: recommend read_io= and write_io= for an export Jeff Layton
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=20261029-master-v2-0-32bfc6ac16da@kernel.org \
--to=jlayton@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=anna@kernel.org \
--cc=cel@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=okorniev@redhat.com \
--cc=snitzer@kernel.org \
--cc=steved@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.