From: Jeff Layton <jlayton@kernel.org>
To: Steve Dickson <steved@redhat.com>
Cc: linux-nfs@vger.kernel.org, Neil Brown <neilb@suse.de>,
Olga Kornievskaia <kolga@netapp.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
Chuck Lever <chuck.lever@oracle.com>,
Lorenzo Bianconi <lorenzo@kernel.org>
Subject: Re: [PATCH nfs-utils v6 0/3] nfsdctl: add a new nfsdctl tool to nfs-utils
Date: Thu, 17 Oct 2024 11:22:30 -0400 [thread overview]
Message-ID: <667e64db1ec556bde001e1c085a259226e6807f3.camel@kernel.org> (raw)
In-Reply-To: <7181e0bd-0fdf-4826-856e-6230f190614f@redhat.com>
On Thu, 2024-10-17 at 07:40 -0400, Steve Dickson wrote:
>
> On 7/22/24 1:01 PM, Jeff Layton wrote:
> > Hi Steve,
> >
> > Here's an squashed version of the nfsdctl patches, that represents
> > the latest changes. Let me know if you run into any other problems,
> > and thanks for helping to test this!
> >
> > Signed-off-by: Jeff Layton <jlayton@kernel.org>
> > ---
> > Changes in v6:
> > - make the default number of threads 16 in autostart
> > - doc updates
> >
> > Changes in v5:
> > - add support for pool-mode setting
> > - fix up the handling of nfsd_netlink.h in autoconf
> > - Link to v4: https://lore.kernel.org/r/20240604-nfsdctl-v4-0-a2941f782e4c@kernel.org
> >
> > Changes in v4:
> > - add ability to specify an array of pool thread counts in nfs.conf
> > - Link to v3: https://lore.kernel.org/r/20240423-nfsdctl-v3-0-9e68181c846d@kernel.org
> >
> > Changes in v3:
> > - split nfsdctl.h so we can include the UAPI header as-is
> > - squash the patches together that added Lorenzo's version and convert
> > it to the new interface
> > - adapt to latest version of netlink interface changes
> > + have THREADS_SET/GET report an array of thread counts (one per pool)
> > + pass scope in as a string to THREADS_SET instead of using unshare() trick
> >
> > Changes in v2:
> > - Adapt to latest kernel netlink interface changes (in particular, send
> > the leastime and gracetime when they are set in the config).
> > - More help text for different subcommands
> > - New nfsdctl(8) manpage
> > - Patch to make systemd preferentially use nfsdctl instead of rpc.nfsd
> > - Link to v1: https://lore.kernel.org/r/20240412-nfsdctl-v1-0-efd6dcebcc04@kernel.org
> >
> > ---
> > Jeff Layton (3):
> > nfsdctl: add the nfsdctl utility to nfs-utils
> > nfsdctl: asciidoc source for the manpage
> > systemd: use nfsdctl to start and stop the nfs server
> >
> > configure.ac | 19 +
> > systemd/nfs-server.service | 4 +-
> > utils/Makefile.am | 4 +
> > utils/nfsdctl/Makefile.am | 13 +
> > utils/nfsdctl/nfsd_netlink.h | 96 +++
> > utils/nfsdctl/nfsdctl.8 | 304 ++++++++
> > utils/nfsdctl/nfsdctl.adoc | 158 +++++
> > utils/nfsdctl/nfsdctl.c | 1570 ++++++++++++++++++++++++++++++++++++++++++
> > utils/nfsdctl/nfsdctl.h | 93 +++
> > 9 files changed, 2259 insertions(+), 2 deletions(-)
> > ---
> > base-commit: b76dbaa48f7c239accb0c2d1e1d51ddd73f4d6be
> > change-id: 20240412-nfsdctl-fa8bd8430cfd
> >
> > Best regards,
> Committed... (tag: nfs-utils-2-7-2-rc2)
>
> Note: These changes need a v6.11 kernel for V3 to
> come up properly
>
Thanks! To be clear:
The "v3 problem" you're referring to was fixed in mainline by:
91da337e5d50 nfsd: don't set SVC_SOCK_ANONYMOUS when creating nfsd sockets
That patch also went into v6.10.5 (as 04c2c4d836ff) as well. Earlier
kernels don't need it since they lack the relevant netlink interfaces
altogether.
--
Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2024-10-17 15:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-22 17:01 [PATCH nfs-utils v6 0/3] nfsdctl: add a new nfsdctl tool to nfs-utils Jeff Layton
2024-07-22 17:01 ` [PATCH nfs-utils v6 1/3] nfsdctl: add the nfsdctl utility " Jeff Layton
2024-07-22 17:01 ` [PATCH nfs-utils v6 2/3] nfsdctl: asciidoc source for the manpage Jeff Layton
2024-07-22 17:01 ` [PATCH nfs-utils v6 3/3] systemd: use nfsdctl to start and stop the nfs server Jeff Layton
2024-07-26 19:40 ` [PATCH nfs-utils v6 0/3] nfsdctl: add a new nfsdctl tool to nfs-utils Steve Dickson
2024-07-26 21:32 ` Jeff Layton
2024-07-26 21:59 ` Steve Dickson
2024-07-26 22:20 ` Jeff Layton
2024-07-27 11:28 ` Steve Dickson
2024-07-27 16:03 ` Chuck Lever III
2024-09-30 15:52 ` Jeff Layton
2024-09-30 16:16 ` Steve Dickson
2024-10-16 15:02 ` Jeff Layton
2024-10-16 20:10 ` Steve Dickson
2024-10-17 11:40 ` Steve Dickson
2024-10-17 15:22 ` Jeff Layton [this message]
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=667e64db1ec556bde001e1c085a259226e6807f3.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=Dai.Ngo@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=kolga@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=neilb@suse.de \
--cc=steved@redhat.com \
--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