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;
Date:   Fri, 19 Jun 2020 16:17:04 -0400
To:     Trishali Nayar <ntrishal@in.ibm.com>
Cc:     linux-nfs@vger.kernel.org
Subject: Re: Trunking Support in 4.1
Message-ID: <20200619201704.GA1564@fieldses.org>
References: <OF8137F6B8.51CF4CA7-ON0025858B.00459213-6525858B.0052D80D@notes.na.collabserv.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <OF8137F6B8.51CF4CA7-ON0025858B.00459213-6525858B.0052D80D@notes.na.collabserv.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
From:   bfields@fieldses.org (J. Bruce Fields)
Sender: linux-nfs-owner@vger.kernel.org
Precedence: bulk

On Thu, Jun 18, 2020 at 08:34:53PM +0530, Trishali Nayar wrote:
> Hi all,
> 
> The 4.1 RFC mentions about two types of trunking: Session trunking and 
> Client ID trunking.
>  
> Are both of these supported by 4.1 servers and clients? 
> 
> And are these mandatory features to claim 4.1 support?

They are mandatory for servers to support, and the Linux server supports
them.

The client makes some use of session trunking with the nconnect mount
option.

--b.

> 
> Your insights will be really useful.
>  
> Thanks and regards,
> Trishali.