All of lore.kernel.org
 help / color / mirror / Atom feed
From: guy keren <guy@vastdata.com>
To: linux-nfs <linux-nfs@vger.kernel.org>
Subject: nfs4.1 and nconnect - is this supported?
Date: Thu, 15 Jul 2021 16:16:19 +0300	[thread overview]
Message-ID: <9d726e22-8c47-41ac-727b-3a27a9919fc6@vastdata.com> (raw)


hi,

i wonder if the linux client's nfs nconnect feature was designed to 
support NFS4.1 (or higher) versions? according to our experimentation, 
the linux client seems to just alternate messages between the multiple 
RPC/TCP connections, and does not seem to adhere to the NFS 4.1 protocol 
requirement, that when using multiple connections, the client needs to 
use BIND_CONN_TO_SESSION when trying to user a 2nd connection with the 
same NFS4.1 session.

was this done on purpose? or is this configuration not supported by 
linux client's 'nconnect'? or am i missing something?

thanks,
--guy

             reply	other threads:[~2021-07-15 13:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-15 13:16 guy keren [this message]
2021-07-15 14:43 ` nfs4.1 and nconnect - is this supported? Rick Macklem
2021-07-15 20:25   ` guy keren

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=9d726e22-8c47-41ac-727b-3a27a9919fc6@vastdata.com \
    --to=guy@vastdata.com \
    --cc=linux-nfs@vger.kernel.org \
    /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.