Message ID | 20211209195335.32404-1-olga.kornievskaia@gmail.com (mailing list archive) |
---|---|
Headers | show |
Series | NFSv4.1+ support for session trunking discovery | expand |
Hi, We need a option to control active-active or active-standby mode? 1) active-active will get better performance when 10GbE/25GbE ports? 2) active-standby will get better performance when 100GbE/40GbE ports? Best Regards Wang Yugui (wangyugui@e16-tech.com) 2021/12/11 > From: Olga Kornievskaia <kolga@netapp.com> > > This patch series adds session trunking discovery and setup. When a > client discovers a new file system in addition to probing for > existing attributes, it also sends a GETATTR asking for an fs_location > attribute. If it receives a non-zero length reply, it will iterate > thru the response and, for each server location, it will establish a > connection (of the same type as the existing RPC transport), send > an EXCHANGE_ID, and test for session trunking. If the trunking test > succeeds, the transport is added to an existing set of transports > for this server. > > Olga Kornievskaia (7): > NFSv4 remove zero number of fs_locations entries error check > NFSv4 store server support for fs_location attribute > NFSv4.1 query for fs_location attr on a new file system > NFSv4 expose nfs_parse_server_name function > NFSv4 handle port presence in fs_location server string > SUNRPC allow for unspecified transport time in rpc_clnt_add_xprt > NFSv4.1 test and add 4.1 trunking transport > > fs/nfs/client.c | 7 ++ > fs/nfs/nfs4_fs.h | 12 ++-- > fs/nfs/nfs4namespace.c | 19 ++++-- > fs/nfs/nfs4proc.c | 131 +++++++++++++++++++++++++++++++++++--- > fs/nfs/nfs4state.c | 6 +- > fs/nfs/nfs4xdr.c | 2 - > include/linux/nfs_fs_sb.h | 2 +- > include/linux/nfs_xdr.h | 1 + > net/sunrpc/clnt.c | 5 +- > 9 files changed, 158 insertions(+), 27 deletions(-) > > -- > 2.27.0
From: Olga Kornievskaia <kolga@netapp.com> This patch series adds session trunking discovery and setup. When a client discovers a new file system in addition to probing for existing attributes, it also sends a GETATTR asking for an fs_location attribute. If it receives a non-zero length reply, it will iterate thru the response and, for each server location, it will establish a connection (of the same type as the existing RPC transport), send an EXCHANGE_ID, and test for session trunking. If the trunking test succeeds, the transport is added to an existing set of transports for this server. Olga Kornievskaia (7): NFSv4 remove zero number of fs_locations entries error check NFSv4 store server support for fs_location attribute NFSv4.1 query for fs_location attr on a new file system NFSv4 expose nfs_parse_server_name function NFSv4 handle port presence in fs_location server string SUNRPC allow for unspecified transport time in rpc_clnt_add_xprt NFSv4.1 test and add 4.1 trunking transport fs/nfs/client.c | 7 ++ fs/nfs/nfs4_fs.h | 12 ++-- fs/nfs/nfs4namespace.c | 19 ++++-- fs/nfs/nfs4proc.c | 131 +++++++++++++++++++++++++++++++++++--- fs/nfs/nfs4state.c | 6 +- fs/nfs/nfs4xdr.c | 2 - include/linux/nfs_fs_sb.h | 2 +- include/linux/nfs_xdr.h | 1 + net/sunrpc/clnt.c | 5 +- 9 files changed, 158 insertions(+), 27 deletions(-)