Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Olga Kornievskaia <olga.kornievskaia@gmail.com>
To:     trond.myklebust@hammerspace.com, anna.schumaker@netapp.com
Cc:     linux-nfs@vger.kernel.org
Subject: [PATCH v2 0/3] don't collapse transports for the trunkable
Date:   Wed,  9 Jun 2021 17:53:16 -0400
Message-Id: <20210609215319.5518-1-olga.kornievskaia@gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

From: Olga Kornievskaia <kolga@netapp.com>

This patch series attempts to allow for new mounts that are to the
same server (ie nfsv4.1+ session trunkable servers) but different
network addresses to use connections associated with those mounts
but still use the same client structure.

A new mount options, "max_connect", controls how many extra transports
can be added to an existing client, with maximum of 128 transports in
total for either nconnect transports (which are multiple connections
but to the same IP) or transports that are going to different network
addresses.

Olga Kornievskaia (3):
  SUNRPC query xprt switch for number of active transports
  NFSv4 introduce max_connect mount options
  NFSv4.1+ add trunking when server trunking detected

 fs/nfs/client.c             |  1 +
 fs/nfs/fs_context.c         |  8 +++++++
 fs/nfs/internal.h           |  2 ++
 fs/nfs/nfs4client.c         | 43 +++++++++++++++++++++++++++++++++++--
 fs/nfs/super.c              |  2 ++
 include/linux/nfs_fs_sb.h   |  1 +
 include/linux/sunrpc/clnt.h |  2 ++
 net/sunrpc/clnt.c           | 13 +++++++++++
 8 files changed, 70 insertions(+), 2 deletions(-)

-- 
2.27.0