From: bfields@fieldses.org (J. Bruce Fields)
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Anna Schumaker <schumaker.anna@gmail.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Anna Schumaker <Anna.Schumaker@Netapp.com>
Subject: Re: [RFC PATCH 0/7] SUNRPC: Create sysfs files for changing IP
Date: Tue, 12 Jan 2021 11:59:11 -0500 [thread overview]
Message-ID: <20210112165911.GH9248@fieldses.org> (raw)
In-Reply-To: <CE510EA5-1E3F-4516-A948-10A0FF31C94F@oracle.com>
On Tue, Jan 12, 2021 at 08:09:09AM -0500, Chuck Lever wrote:
> Hi Anna-
>
> > On Jan 11, 2021, at 4:41 PM, schumaker.anna@gmail.com wrote:
> >
> > From: Anna Schumaker <Anna.Schumaker@Netapp.com>
> >
> > It's possible for an NFS server to go down but come back up with a
> > different IP address. These patches provide a way for administrators to
> > handle this issue by providing a new IP address for xprt sockets to
> > connect to.
> >
> > This is a first draft of the code, so any thoughts or suggestions would
> > be greatly appreciated!
>
> One implementation question, one future question.
>
> Would /sys/kernel/net be a little better? or /sys/kernel/sunrpc ?
>
> Do you have a plan to integrate support for fs_locations to probe
> servers for alternate IP addresses? Would that be a userspace
> utility that would plug values into this new /sys API?
We already have dns resolution for fs_locations, right? Why can't we
use that here? Is it that the mount call doesn't give us a host name?
Or we don't trust dns to have the updated IP address for some reason?
--b.
>
>
> > Anna
> >
> >
> > Anna Schumaker (7):
> > net: Add a /sys/net directory to sysfs
> > sunrpc: Create a sunrpc directory under /sys/net/
> > sunrpc: Create a net/ subdirectory in the sunrpc sysfs
> > sunrpc: Create per-rpc_clnt sysfs kobjects
> > sunrpc: Create a per-rpc_clnt file for managing the IP address
> > sunrpc: Prepare xs_connect() for taking NULL tasks
> > sunrpc: Connect to a new IP address provided by the user
> >
> > include/linux/sunrpc/clnt.h | 1 +
> > include/net/sock.h | 4 +
> > net/socket.c | 8 ++
> > net/sunrpc/Makefile | 2 +-
> > net/sunrpc/clnt.c | 5 ++
> > net/sunrpc/sunrpc_syms.c | 8 ++
> > net/sunrpc/sysfs.c | 160 ++++++++++++++++++++++++++++++++++++
> > net/sunrpc/sysfs.h | 22 +++++
> > net/sunrpc/xprtsock.c | 3 +-
> > 9 files changed, 211 insertions(+), 2 deletions(-)
> > create mode 100644 net/sunrpc/sysfs.c
> > create mode 100644 net/sunrpc/sysfs.h
> >
> > --
> > 2.29.2
> >
>
> --
> Chuck Lever
>
>
next prev parent reply other threads:[~2021-01-12 17:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 21:41 [RFC PATCH 0/7] SUNRPC: Create sysfs files for changing IP schumaker.anna
2021-01-11 21:41 ` [RFC PATCH 1/7] net: Add a /sys/net directory to sysfs schumaker.anna
2021-01-11 21:41 ` [RFC PATCH 2/7] sunrpc: Create a sunrpc directory under /sys/net/ schumaker.anna
2021-01-11 21:41 ` [RFC PATCH 3/7] sunrpc: Create a net/ subdirectory in the sunrpc sysfs schumaker.anna
2021-01-11 21:41 ` [RFC PATCH 4/7] sunrpc: Create per-rpc_clnt sysfs kobjects schumaker.anna
2021-01-11 21:41 ` [RFC PATCH 5/7] sunrpc: Create a per-rpc_clnt file for managing the IP address schumaker.anna
2021-01-17 12:59 ` [sunrpc] 4c73715aa6: WARNING:suspicious_RCU_usage kernel test robot
2021-01-17 12:59 ` kernel test robot
2021-01-11 21:41 ` [RFC PATCH 6/7] sunrpc: Prepare xs_connect() for taking NULL tasks schumaker.anna
2021-01-11 21:41 ` [RFC PATCH 7/7] sunrpc: Connect to a new IP address provided by the user schumaker.anna
2021-01-12 13:09 ` [RFC PATCH 0/7] SUNRPC: Create sysfs files for changing IP Chuck Lever
2021-01-12 16:59 ` J. Bruce Fields [this message]
2021-01-13 19:23 ` Anna Schumaker
2021-01-13 19:48 ` Chuck Lever
2021-01-13 21:23 ` Chuck Lever
2021-01-14 20:29 ` Olga Kornievskaia
2021-01-19 15:55 ` 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=20210112165911.GH9248@fieldses.org \
--to=bfields@fieldses.org \
--cc=Anna.Schumaker@Netapp.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=schumaker.anna@gmail.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 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.