All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wang Yugui <wangyugui@e16-tech.com>
To: Olga Kornievskaia <olga.kornievskaia@gmail.com>
Cc: trond.myklebust@hammerspace.com, anna.schumaker@netapp.com,
	linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/7] NFSv4.1+ support for session trunking discovery
Date: Sat, 11 Dec 2021 19:39:36 +0800	[thread overview]
Message-ID: <20211211193935.C17A.409509F4@e16-tech.com> (raw)
In-Reply-To: <20211209195335.32404-1-olga.kornievskaia@gmail.com>

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



      parent reply	other threads:[~2021-12-11 11:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-09 19:53 [PATCH 0/7] NFSv4.1+ support for session trunking discovery Olga Kornievskaia
2021-12-09 19:53 ` [PATCH 1/7] NFSv4 remove zero number of fs_locations entries error check Olga Kornievskaia
2021-12-09 19:53 ` [PATCH 2/7] NFSv4 store server support for fs_location attribute Olga Kornievskaia
2021-12-09 19:53 ` [PATCH 3/7] NFSv4.1 query for fs_location attr on a new file system Olga Kornievskaia
2021-12-09 19:53 ` [PATCH 4/7] NFSv4 expose nfs_parse_server_name function Olga Kornievskaia
2021-12-09 19:53 ` [PATCH 5/7] NFSv4 handle port presence in fs_location server string Olga Kornievskaia
2021-12-09 19:53 ` [PATCH 6/7] SUNRPC allow for unspecified transport time in rpc_clnt_add_xprt Olga Kornievskaia
2021-12-09 19:53 ` [PATCH 7/7] NFSv4.1 test and add 4.1 trunking transport Olga Kornievskaia
2021-12-11 11:39 ` Wang Yugui [this message]

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=20211211193935.C17A.409509F4@e16-tech.com \
    --to=wangyugui@e16-tech.com \
    --cc=anna.schumaker@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=olga.kornievskaia@gmail.com \
    --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 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.