linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bfields@fieldses.org (J. Bruce Fields)
To: Trishali Nayar <ntrishal@in.ibm.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Trunking Support in 4.1
Date: Fri, 19 Jun 2020 16:17:04 -0400	[thread overview]
Message-ID: <20200619201704.GA1564@fieldses.org> (raw)
In-Reply-To: <OF8137F6B8.51CF4CA7-ON0025858B.00459213-6525858B.0052D80D@notes.na.collabserv.com>

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.

      reply	other threads:[~2020-06-19 20:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-18 15:04 Trunking Support in 4.1 Trishali Nayar
2020-06-19 20:17 ` J. Bruce Fields [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=20200619201704.GA1564@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=ntrishal@in.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).