From: Dan Aloni <dan@kernelim.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Trond Myklebust <trond.myklebust@hammerspace.com>,
Anna Schumaker <anna.schumaker@netapp.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Jim Foraker <foraker1@llnl.gov>, Ben Woodard <woodard@redhat.com>
Subject: Re: [RFC] NFSv3 RDMA multipath enhancements
Date: Thu, 21 Jan 2021 20:58:13 +0200 [thread overview]
Message-ID: <20210121185813.GA3135951@gmail.com> (raw)
In-Reply-To: <3AB7389B-2EA9-4894-9656-9C8512166E0E@oracle.com>
On Wed, Jan 13, 2021 at 09:59:58AM -0500, Chuck Lever wrote:
> > To my understanding NFSv4.x with pNFS has advanced dynamic transport
> > management logic along file layouts supporting stripe over file offsets,
> > however there are cases in which we would like to achieve good
> > performance even with the older protocol.
>
> Hi Dan, my curiosity is piqued about the RPC request dispatch changes
> you have in mind. Can you post them here for review?
These changes depend on the initial changes I'd like to contribute. The
gist of them concerns the xprt multipath algorithm where in addition to
round robin, we add further considerations regarding transport picking.
For example, for data IOs, the NUMA node to which the memory pages
attached to the RPC request may be used to pick a transport with an
outgoing local port that is closer to that memory in the server
architecture compared to the other local ports. So the idea is to lessen
data transfer bottlenecks in hardware.
> Also, if you can tell us, what NFS server supports NFS/RDMA but not
> NFSv4 ?
For example, there are VAST Data clusters currently supporting NFSv3 (as
one logical server), with the NFSv4 support coming soon.
--
Dan Aloni
prev parent reply other threads:[~2021-01-21 19:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 14:17 [RFC] NFSv3 RDMA multipath enhancements Dan Aloni
2021-01-13 14:59 ` Chuck Lever
2021-01-21 18:58 ` Dan Aloni [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=20210121185813.GA3135951@gmail.com \
--to=dan@kernelim.com \
--cc=anna.schumaker@netapp.com \
--cc=chuck.lever@oracle.com \
--cc=foraker1@llnl.gov \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@hammerspace.com \
--cc=woodard@redhat.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).