linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Bart Van Assche <bvanassche@acm.org>,
	linux-rdma <linux-rdma@vger.kernel.org>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	Lijun Ou <oulijun@huawei.com>,
	umalhi@cisco.com, zhongjiang@huawei.com,
	venkata.s.dhanalakota@intel.com,
	Dennis Dalessandro <dennis.dalessandro@intel.com>
Subject: Re: [PATCH v1 1/4] xprtrdma: Remove support for FMR memory registration
Date: Mon, 19 Nov 2018 16:10:32 -0700	[thread overview]
Message-ID: <20181119231032.GO4890@ziepe.ca> (raw)
In-Reply-To: <1172062C-E8CB-4F37-905D-F40EC8D9270C@oracle.com>

On Mon, Nov 19, 2018 at 05:56:54PM -0500, Chuck Lever wrote:
> 
> 
> > On Nov 19, 2018, at 5:41 PM, Jason Gunthorpe <jgg@ziepe.ca> wrote:
> > 
> > On Mon, Nov 19, 2018 at 08:16:37AM -0800, Bart Van Assche wrote:
> >> 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
> > 
> > Ooh, qib was not in the list when we talked on this in plumbers. That
> > does change things. 
> > 
> > Dennis: Could qib be changed? HFI1 supports FRWR right?
> > 
> >>> - 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?
> > 
> > Ignore usnic, it is not a RDMA driver
> > 
> >> Can someone from Huawei comment on how many of their customers rely on the hns
> >> driver?
> > 
> > Nor was this, this is an actively used driver..
> > 
> > Could hns do FRWR? It is very disappointing that such a new driver
> > does not support FRWR.
> > 
> > I guess it is worth stating again that FMR is deprecated. People are
> > going to be disappointed if they try to submit new drivers that don't
> > support FRWR :(
> 
> My methodology was to search for whether each driver asserts
> IB_DEVICE_MEM_MGT_EXTENSIONS in device_cap_flags.

Drivers might be broken here, or we might need more flags.

Searching for FWMR shows hits in hns, which is encouraging...

Jason

  reply	other threads:[~2018-11-19 23:10 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
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 [this message]
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=20181119231032.GO4890@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=bvanassche@acm.org \
    --cc=chuck.lever@oracle.com \
    --cc=dennis.dalessandro@intel.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;
as well as URLs for NNTP newsgroup(s).