From: schumaker.anna@gmail.com
To: steved@redhat.com, linux-nfs@vger.kernel.org
Cc: Anna.Schumaker@Netapp.com
Subject: [PATCH v2 0/9] Add a tool for using the new sysfs files
Date: Fri, 6 Aug 2021 16:17:30 -0400 [thread overview]
Message-ID: <20210806201739.472806-1-Anna.Schumaker@Netapp.com> (raw)
From: Anna Schumaker <Anna.Schumaker@Netapp.com>
These patches implement a tool that can be used to read and write the
sysfs files, with subcommands! They do need my extra patches to add in
srcaddr and dst_port to the xprt_info file. Let me know if I need to
resend adding support for kernels both with and without these patches.
The following subcommands are implemented:
nfs-sysfs.py rpc-client
nfs-sysfs.py xprt
nfs-sysfs.py xprt set
nfs-sysfs.py xprt-switch
nfs-sysfs.py xprt-switch set
So you can print out information about every xprt-switch with:
anna@client ~ % nfs-sysfs xprt-switch
switch 0: num_xprts 1, num_active 1, queue_len 0
xprt 0: local, /var/run/gssproxy.sock [main]
switch 1: num_xprts 1, num_active 1, queue_len 0
xprt 1: local, /var/run/rpcbind.sock [main]
switch 2: num_xprts 1, num_active 1, queue_len 0
xprt 2: tcp, 192.168.111.1 [main]
switch 3: num_xprts 4, num_active 4, queue_len 0
xprt 3: tcp, 192.168.111.188 [main]
xprt 4: tcp, 192.168.111.188
xprt 5: tcp, 192.168.111.188
xprt 6: tcp, 192.168.111.188
And information about each xprt:
anna@client ~ % nfs-sysfs xprt
xprt 0: local, /var/run/gssproxy.sock, port 0, state <MAIN,CONNECTED,BOUND>
Source: (einval), port 0, Requests: 2
Congestion: cur 0, win 256, Slots: min 2, max 65536
Queues: binding 0, sending 0, pending 0, backlog 0, tasks 0
xprt 1: local, /var/run/rpcbind.sock, port 0, state <MAIN,CONNECTED,BOUND>
Source: (einval), port 0, Requests: 2
Congestion: cur 0, win 256, Slots: min 2, max 65536
Queues: binding 0, sending 0, pending 0, backlog 0, tasks 0
xprt 2: tcp, 192.168.111.1, port 2049, state <MAIN,CONNECTED,BOUND>
Source: 192.168.111.222, port 959, Requests: 2
Congestion: cur 0, win 256, Slots: min 2, max 65536
Queues: binding 0, sending 0, pending 0, backlog 0, tasks 0
xprt 3: tcp, 192.168.111.188, port 2049, state <MAIN,CONNECTED,BOUND>
Source: 192.168.111.222, port 921, Requests: 2
Congestion: cur 0, win 256, Slots: min 2, max 65536
Queues: binding 0, sending 0, pending 0, backlog 0, tasks 0
xprt 4: tcp, 192.168.111.188, port 2049, state <CONNECTED,BOUND>
Source: 192.168.111.222, port 726, Requests: 2
Congestion: cur 0, win 256, Slots: min 2, max 65536
Queues: binding 0, sending 0, pending 0, backlog 0, tasks 0
xprt 5: tcp, 192.168.111.188, port 2049, state <CONNECTED,BOUND>
Source: 192.168.111.222, port 671, Requests: 2
Congestion: cur 0, win 256, Slots: min 2, max 65536
Queues: binding 0, sending 0, pending 0, backlog 0, tasks 0
xprt 6: tcp, 192.168.111.188, port 2049, state <CONNECTED,BOUND>
Source: 192.168.111.222, port 934, Requests: 2
Congestion: cur 0, win 256, Slots: min 2, max 65536
Queues: binding 0, sending 0, pending 0, backlog 0, tasks 0
You can use the `set` subcommand to change the dstaddr of individual xprts:
anna@client ~ % sudo nfs-sysfs xprt --id 4
xprt 4: tcp, 192.168.111.188, port 2049, state <CONNECTED,BOUND>
Source: 192.168.111.222, port 726, Requests: 2
Congestion: cur 0, win 256, Slots: min 2, max 65536
Queues: binding 0, sending 0, pending 0, backlog 0, tasks 0
anna@client ~ % sudo nfs-sysfs xprt set --id 4 --dstaddr server2.nowheycreamery.com
xprt 4: tcp, 192.168.111.186, port 2049, state <CONNECTED,BOUND>
Source: 192.168.111.222, port 726, Requests: 2
Congestion: cur 0, win 256, Slots: min 2, max 65536
Queues: binding 0, sending 0, pending 0, backlog 0, tasks 0
Or for changing the dstaddr of all xprts attached to a switch:
anna@client % ./nfs-sysfs.py xprt-switch --id 3
switch 3: num_xprts 4, num_active 4, queue_len 0
xprt 3: tcp, 192.168.111.188 [main]
xprt 4: tcp, 192.168.111.188
xprt 5: tcp, 192.168.111.188
xprt 6: tcp, 192.168.111.188
anna@client % sudo ./nfs-sysfs.py xprt-switch set --id 4 --dstaddr server2.nowheycreamery.vm
switch 3: num_xprts 4, num_active 4, queue_len 0
xprt 2: tcp, 192.168.111.186 [main]
xprt 3: tcp, 192.168.111.186
xprt 5: tcp, 192.168.111.186
xprt 6: tcp, 192.168.111.186
What does everybody think? Is there any thing I should change about the
user input or output lines? How about other subcommands that should be
added with the initial submission?
Thanks,
Anna
Anna Schumaker (9):
nfs-sysfs: Add an nfs-sysfs.py tool
nfs-sysfs.py: Add a command for printing xprt switch information
nfs-sysfs.py: Add a command for printing individual xprts
nfs-sysfs.py: Add a command for printing rpc-client information
nfs-sysfs.py: Add a command for changing xprt dstaddr
nfs-sysfs.py: Add a command for changing xprt-switch dstaddrs
nfs-sysfs.py: Add a command for changing xprt state
nfs-sysfs: Add a man page
nfs-sysfs: Add installation to the Makefile
.gitignore | 2 +
configure.ac | 1 +
tools/Makefile.am | 2 +-
tools/nfs-sysfs/Makefile.am | 20 +++++++
tools/nfs-sysfs/client.py | 27 +++++++++
tools/nfs-sysfs/nfs-sysfs | 5 ++
tools/nfs-sysfs/nfs-sysfs.man | 88 +++++++++++++++++++++++++++++
tools/nfs-sysfs/nfs-sysfs.py | 23 ++++++++
tools/nfs-sysfs/switch.py | 51 +++++++++++++++++
tools/nfs-sysfs/sysfs.py | 28 ++++++++++
tools/nfs-sysfs/xprt.py | 101 ++++++++++++++++++++++++++++++++++
11 files changed, 347 insertions(+), 1 deletion(-)
create mode 100644 tools/nfs-sysfs/Makefile.am
create mode 100644 tools/nfs-sysfs/client.py
create mode 100644 tools/nfs-sysfs/nfs-sysfs
create mode 100644 tools/nfs-sysfs/nfs-sysfs.man
create mode 100755 tools/nfs-sysfs/nfs-sysfs.py
create mode 100644 tools/nfs-sysfs/switch.py
create mode 100644 tools/nfs-sysfs/sysfs.py
create mode 100644 tools/nfs-sysfs/xprt.py
--
2.32.0
next reply other threads:[~2021-08-06 20:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-06 20:17 schumaker.anna [this message]
2021-08-06 20:17 ` [PATCH v2 1/9] nfs-sysfs: Add an nfs-sysfs.py tool schumaker.anna
2021-08-17 16:57 ` Mora, Jorge
2021-08-23 21:41 ` Anna Schumaker
2021-08-06 20:17 ` [PATCH v2 2/9] nfs-sysfs.py: Add a command for printing xprt switch information schumaker.anna
2021-08-06 20:17 ` [PATCH v2 3/9] nfs-sysfs.py: Add a command for printing individual xprts schumaker.anna
2021-08-06 20:17 ` [PATCH v2 4/9] nfs-sysfs.py: Add a command for printing rpc-client information schumaker.anna
2021-08-06 20:17 ` [PATCH v2 5/9] nfs-sysfs.py: Add a command for changing xprt dstaddr schumaker.anna
2021-08-06 20:17 ` [PATCH v2 6/9] nfs-sysfs.py: Add a command for changing xprt-switch dstaddrs schumaker.anna
2021-08-06 20:17 ` [PATCH v2 7/9] nfs-sysfs.py: Add a command for changing xprt state schumaker.anna
2021-08-17 17:00 ` Mora, Jorge
2021-08-06 20:17 ` [PATCH v2 8/9] nfs-sysfs: Add a man page schumaker.anna
2021-08-06 20:17 ` [PATCH v2 9/9] nfs-sysfs: Add installation to the Makefile schumaker.anna
2021-08-08 16:30 ` [PATCH v2 0/9] Add a tool for using the new sysfs files Steve Dickson
2021-08-08 19:00 ` Anna Schumaker
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=20210806201739.472806-1-Anna.Schumaker@Netapp.com \
--to=schumaker.anna@gmail.com \
--cc=Anna.Schumaker@Netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.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