From: Dan Aloni <dan@kernelim.com>
To: linux-nfs@vger.kernel.org, Anna Schumaker <anna.schumaker@netapp.com>
Cc: Trond Myklebust <trond.myklebust@hammerspace.com>
Subject: [PATCH v1 0/8] sysfs files for multipath transport control
Date: Mon, 15 Feb 2021 19:39:54 +0200 [thread overview]
Message-ID: <20210215174002.2376333-1-dan@kernelim.com> (raw)
Hi Anna,
This patchset builds ontop v2 of your 'sysfs files for changing IP' changeset.
- The patchset adds two more sysfs objects, for one for transport and another
for multipath.
- Also, `net` renamed to `client`, and `client` now has symlink to its principal
transport. A client also has a symlink to its `multipath` object.
- The transport interface lets you change `dstaddr` of individual transports,
when `nconnect` is used (or if it wasn't used and these were added with the
new interface).
- The interface to add a transport is using a single string written to 'add',
for example:
echo 'dstaddr 192.168.40.8 kind rdma' \
> /sys/kernel/sunrpc/client/0/multipath/add
These changes are independent of the method used to obtain a sunrpc ID for a
mountpoint. For that I've sent a concept patch showing an fspick-based
implementation: https://marc.info/?l=linux-nfs&m=161332454821849&w=4
Thanks
Dan Aloni (8):
sunrpc: rename 'net' to 'client'
sunrpc: add xprt id
sunrpc: add a directory per sunrpc xprt
sunrpc: have client directory a symlink to the root transport
sunrpc: add IDs to multipath
sunrpc: add multipath directory and symlink from client
sunrpc: change rpc_clnt_add_xprt() to rpc_add_xprt()
sunrpc: introduce an 'add' node to 'multipath' sysfs directory
fs/nfs/pnfs_nfs.c | 12 +-
include/linux/sunrpc/clnt.h | 12 +-
include/linux/sunrpc/xprt.h | 3 +
include/linux/sunrpc/xprtmultipath.h | 6 +
net/sunrpc/clnt.c | 39 +--
net/sunrpc/sunrpc_syms.c | 2 +
net/sunrpc/sysfs.c | 403 +++++++++++++++++++++++----
net/sunrpc/sysfs.h | 21 +-
net/sunrpc/xprt.c | 29 ++
net/sunrpc/xprtmultipath.c | 37 +++
10 files changed, 487 insertions(+), 77 deletions(-)
--
2.26.2
next reply other threads:[~2021-02-15 17:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 17:39 Dan Aloni [this message]
2021-02-15 17:39 ` [PATCH v1 1/8] sunrpc: rename 'net' to 'client' Dan Aloni
2021-02-16 21:24 ` Anna Schumaker
2021-02-17 18:58 ` Dan Aloni
2021-02-15 17:39 ` [PATCH v1 2/8] sunrpc: add xprt id Dan Aloni
2021-02-15 17:39 ` [PATCH v1 3/8] sunrpc: add a directory per sunrpc xprt Dan Aloni
2021-02-16 21:46 ` Anna Schumaker
2021-02-17 19:01 ` Dan Aloni
2021-02-15 17:39 ` [PATCH v1 4/8] sunrpc: have client directory a symlink to the root transport Dan Aloni
2021-02-15 17:39 ` [PATCH v1 5/8] sunrpc: add IDs to multipath Dan Aloni
2021-02-15 17:40 ` [PATCH v1 6/8] sunrpc: add multipath directory and symlink from client Dan Aloni
2021-02-15 17:40 ` [PATCH v1 7/8] sunrpc: change rpc_clnt_add_xprt() to rpc_add_xprt() Dan Aloni
2021-02-15 17:40 ` [PATCH v1 8/8] sunrpc: introduce an 'add' node to 'multipath' sysfs directory Dan Aloni
2021-03-02 3:56 ` [PATCH v1 0/8] sysfs files for multipath transport control Olga Kornievskaia
2021-03-04 11:58 ` Dan Aloni
2021-03-04 18:39 ` Chuck Lever
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=20210215174002.2376333-1-dan@kernelim.com \
--to=dan@kernelim.com \
--cc=anna.schumaker@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@hammerspace.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