From: Lorenzo Bianconi <lorenzo@kernel.org>
To: linux-nfs@vger.kernel.org
Cc: lorenzo.bianconi@redhat.com, neilb@suse.de,
netdev@vger.kernel.org, jlayton@kernel.org, kuba@kernel.org
Subject: [PATCH v5 0/3] convert write_threads, write_version and write_ports to netlink commands
Date: Wed, 29 Nov 2023 18:12:42 +0100 [thread overview]
Message-ID: <cover.1701277475.git.lorenzo@kernel.org> (raw)
Introduce write_threads, write_version and write_ports netlink
commands similar to the ones available through the procfs.
Changes since v4:
- rebase on top of nfsd-next tree
Changes since v3:
- drop write_maxconn and write_maxblksize for the moment
- add write_version and write_ports commands
Changes since v2:
- use u32 to store nthreads in nfsd_nl_threads_set_doit
- rename server-attr in control-plane in nfsd.yaml specs
Changes since v1:
- remove write_v4_end_grace command
- add write_maxblksize and write_maxconn netlink commands
This patch can be tested with user-space tool reported below:
https://github.com/LorenzoBianconi/nfsd-netlink.git
Lorenzo Bianconi (3):
NFSD: convert write_threads to netlink command
NFSD: convert write_version to netlink command
NFSD: convert write_ports to netlink command
Documentation/netlink/specs/nfsd.yaml | 83 ++++++++
fs/nfsd/netlink.c | 54 ++++++
fs/nfsd/netlink.h | 8 +
fs/nfsd/nfsctl.c | 267 +++++++++++++++++++++++++-
include/uapi/linux/nfsd_netlink.h | 30 +++
tools/net/ynl/generated/nfsd-user.c | 254 ++++++++++++++++++++++++
tools/net/ynl/generated/nfsd-user.h | 156 +++++++++++++++
7 files changed, 845 insertions(+), 7 deletions(-)
--
2.43.0
next reply other threads:[~2023-11-29 17:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 17:12 Lorenzo Bianconi [this message]
2023-11-29 17:12 ` [PATCH v5 1/3] NFSD: convert write_threads to netlink command Lorenzo Bianconi
2023-11-29 18:13 ` Jeff Layton
2023-11-29 18:31 ` Chuck Lever
2023-11-30 0:32 ` Jakub Kicinski
2023-11-29 17:12 ` [PATCH v5 2/3] NFSD: convert write_version " Lorenzo Bianconi
2023-11-29 18:23 ` Jeff Layton
2023-11-30 9:45 ` Lorenzo Bianconi
2023-11-30 16:17 ` Jeff Layton
2023-11-30 16:11 ` Chuck Lever
2023-11-30 16:25 ` Lorenzo Bianconi
2023-11-30 16:29 ` Chuck Lever
2023-11-30 16:32 ` Lorenzo Bianconi
2023-11-30 0:28 ` Jakub Kicinski
2023-11-30 10:32 ` Lorenzo Bianconi
2023-12-01 7:28 ` Jakub Kicinski
2023-12-05 20:33 ` Simon Horman
2023-11-29 17:12 ` [PATCH v5 3/3] NFSD: convert write_ports " Lorenzo Bianconi
2023-11-29 18:28 ` Jeff Layton
2023-11-30 9:57 ` Lorenzo Bianconi
2023-11-30 16:22 ` Jeff Layton
2023-11-30 16:55 ` Jeff Layton
2023-11-30 17:39 ` Chuck Lever
2023-11-30 18:01 ` Jeff Layton
2023-11-30 18:34 ` Chuck Lever
2023-12-05 20:37 ` Simon Horman
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=cover.1701277475.git.lorenzo@kernel.org \
--to=lorenzo@kernel.org \
--cc=jlayton@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=neilb@suse.de \
--cc=netdev@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 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.