public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Chuck Lever <chuck.lever@oracle.com>, linux-rdma@vger.kernel.org
Cc: linux-nfs@vger.kernel.org, oulijun@huawei.com, umalhi@cisco.com,
	zhongjiang@huawei.com, venkata.s.dhanalakota@intel.com
Subject: Re: [PATCH v1 1/4] xprtrdma: Remove support for FMR memory registration
Date: Mon, 19 Nov 2018 08:16:37 -0800	[thread overview]
Message-ID: <1542644197.185366.50.camel@acm.org> (raw)
In-Reply-To: <20181119154551.10832.5498.stgit@manet.1015granger.net>

On Mon, 2018-11-19 at 10:45 -0500, Chuck Lever wrote:
> FMR is not supported on most recent RDMA devices. It is also slower
> and less secure than FRWR. As discussed during the RDMA BoF at LPC
> 2018, it is time to remove support for FMR in the NFS/RDMA client
> stack. NFS/RDMA server-side uses either local memory registration or
> FRWR.  There is no change required there to deprecate FMR.
> 
> There are a few Infiniband/RoCE devices in the kernel tree that do
> not support MEM_MGT_EXTENSIONS, and therefore will no longer support
> client-side NFS/RDMA. These are:
> 
>  - mthca
>  - qib
>  - usnic
>  - hns (RoCE)

Can someone from Intel comment on how many of their customers rely on the qib
driver?

Can someone from Cisco comment on how many of their customers rely on the usnic
driver?

Can someone from Huawei comment on how many of their customers rely on the hns
driver?

I'm wondering whether I can remove FMR support from the SRP initiator driver.

Thanks,

Bart.

  reply	other threads:[~2018-11-19 16:16 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-19 15:45 [PATCH v1 0/4] NFS/RDMA client for v4.21 (part 1) Chuck Lever
2018-11-19 15:45 ` [PATCH v1 1/4] xprtrdma: Remove support for FMR memory registration Chuck Lever
2018-11-19 16:16   ` Bart Van Assche [this message]
2018-11-19 19:09     ` Leon Romanovsky
2018-11-19 20:52       ` Bart Van Assche
2018-11-20  5:37         ` Leon Romanovsky
2018-11-19 22:41     ` Jason Gunthorpe
2018-11-19 22:56       ` Chuck Lever
2018-11-19 23:10         ` Jason Gunthorpe
2018-11-20 15:22       ` Dennis Dalessandro
2018-11-19 15:45 ` [PATCH v1 2/4] xprtrdma: mrs_create off-by-one Chuck Lever
2018-11-19 15:46 ` [PATCH v1 3/4] xprtrdma: Reduce max_frwr_depth Chuck Lever
2018-11-19 15:46 ` [PATCH v1 4/4] xprtrdma: Plant XID in on-the-wire RDMA offset (FRWR) Chuck Lever
2018-11-19 17:47   ` Olga Kornievskaia
2018-11-19 17:58     ` Chuck Lever
2018-11-19 18:08       ` Olga Kornievskaia
2018-11-19 18:18         ` Chuck Lever
2018-11-19 18:47           ` Olga Kornievskaia
2018-11-19 18:58             ` Chuck Lever
2018-11-19 21:22               ` Olga Kornievskaia
2018-11-19 21:32                 ` Chuck Lever
2018-11-19 21:42                   ` Mora, Jorge
2018-11-19 22:46                     ` Jason Gunthorpe
2018-11-20  2:45                       ` Tom Talpey
2018-11-20  3:09                         ` Jason Gunthorpe
2018-11-20  3:25                           ` Tom Talpey
2018-11-20  3:32                             ` Jason Gunthorpe
2018-11-20  3:38                               ` Tom Talpey
2018-11-20 18:02   ` Anna Schumaker
2018-11-20 18:07     ` Chuck Lever
     [not found]       ` <94ff7ec712e086bfdd9c217a5f97c293a07151b9.camel@gmail.com>
2018-11-20 21:31         ` Chuck Lever

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=1542644197.185366.50.camel@acm.org \
    --to=bvanassche@acm.org \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=oulijun@huawei.com \
    --cc=umalhi@cisco.com \
    --cc=venkata.s.dhanalakota@intel.com \
    --cc=zhongjiang@huawei.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