From: Dennis Dalessandro <dennis.dalessandro@intel.com>
To: Jason Gunthorpe <jgg@mellanox.com>
Cc: Leon Romanovsky <leon@kernel.org>,
Max Gurtovoy <maxg@mellanox.com>,
bvanassche@acm.org, linux-rdma@vger.kernel.org,
dledford@redhat.com, sagi@grimberg.me, israelr@mellanox.com,
shlomin@mellanox.com, "Marciniszyn,
Mike" <mike.marciniszyn@intel.com>
Subject: Re: [PATCH 0/8 v1] Remove FMR support from RDMA drivers
Date: Tue, 19 May 2020 10:37:07 -0400 [thread overview]
Message-ID: <5563b8da-faf3-1af5-33d0-fe5a6d7291a1@intel.com> (raw)
In-Reply-To: <20200519143030.GA23839@mellanox.com>
On 5/19/2020 10:30 AM, Jason Gunthorpe wrote:
> On Tue, May 19, 2020 at 10:26:37AM -0400, Dennis Dalessandro wrote:
>> On 5/19/2020 10:19 AM, Leon Romanovsky wrote:
>>> On Tue, May 19, 2020 at 10:53:52AM -0300, Jason Gunthorpe wrote:
>>>> On Tue, May 19, 2020 at 09:43:14AM -0400, Dennis Dalessandro wrote:
>>>>> On 5/18/2020 2:10 PM, Jason Gunthorpe wrote:
>>>>>> On Mon, May 18, 2020 at 11:20:04AM -0400, Dennis Dalessandro wrote:
>>>>>>> On 5/14/2020 8:02 AM, Max Gurtovoy wrote:
>>>>>>>> This series removes the support for FMR mode to register memory. This ancient
>>>>>>>> mode is unsafe and not maintained/tested in the last few years. It also doesn't
>>>>>>>> have any reasonable advantage over other memory registration methods such as
>>>>>>>> FRWR (that is implemented in all the recent RDMA adapters). This series should
>>>>>>>> be reviewed and approved by the maintainer of the effected drivers and I
>>>>>>>> suggest to test it as well.
>>>>>>>>
>>>>>>>> The tests that I made for this series (fio benchmarks and fio verify data):
>>>>>>>> 1. iSER initiator on ConnectX-4
>>>>>>>> 2. iSER initiator on ConnectX-3
>>>>>>>> 3. SRP initiator on ConnectX-4 (loopback to SRP target)
>>>>>>>> 4. SRP initiator on ConnectX-3
>>>>>>>>
>>>>>>>> Not tested:
>>>>>>>> 1. RDS
>>>>>>>> 2. mthca
>>>>>>>> 3. rdmavt
>>>>>>>
>>>>>>> This will effectively kill qib which uses rdmavt. It's gonna have to be a
>>>>>>> NAK from me.
>>>>>>
>>>>>> Are you objecting the SRP and iSER changes too?
>>>>>
>>>>> No, just want to keep basic verbs support at least. NFS already dropped,
>>>>> similarly we are ok with dropping it from SRP/iSER as a next step.
>>>>
>>>> So you see a major user in RDS for qib?
>>>
>>> Didn't we agree to drop it from RDS too?
>>>
>>
>> Just basic verbs application support is enough for qib I think. I don't see
>> any major use of RDS.
>
> Well, once the in-kernel users of an API are gone that API will be
> purged. This is standard kernel policy.
>
> So you can't NAK this series on the grounds you want to keep an API
> without users, presumably for out of tree modules...
>
Maybe I need to look at this again. I thought it would kill off user
access as well. We don't need any kernel ULPs.
-Denny
next prev parent reply other threads:[~2020-05-19 14:37 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 12:02 [PATCH 0/8 v1] Remove FMR support from RDMA drivers Max Gurtovoy
2020-05-14 12:02 ` [PATCH 1/8] RDMA/mlx4: remove FMR support for memory registration Max Gurtovoy
2020-05-14 12:02 ` [PATCH 2/8] RDMA/rds: " Max Gurtovoy
2020-05-14 12:03 ` [PATCH 3/8] RDMA/mthca: " Max Gurtovoy
2020-05-14 12:03 ` [PATCH 4/8] RDMA/rdmavt: remove FMR " Max Gurtovoy
2020-05-14 12:03 ` [PATCH 5/8] RDMA/iser: Remove support for " Max Gurtovoy
2020-05-14 12:03 ` [PATCH 6/8] RDMA/srp: remove " Max Gurtovoy
2020-05-14 14:02 ` Bart Van Assche
2020-05-14 12:03 ` [PATCH 7/8] RDMA/core: remove FMR pool API Max Gurtovoy
2020-05-14 12:03 ` [PATCH 8/8] RDMA/core: remove FMR device ops Max Gurtovoy
2020-05-14 15:13 ` [PATCH 0/8 v1] Remove FMR support from RDMA drivers Aron Silverton
2020-05-14 18:18 ` santosh.shilimkar
2020-05-14 19:42 ` Max Gurtovoy
2020-05-14 22:23 ` Sagi Grimberg
2020-05-14 23:41 ` santosh.shilimkar
2020-05-15 16:52 ` Tom Talpey
2020-05-15 18:59 ` Sagi Grimberg
2020-05-17 10:51 ` Max Gurtovoy
2020-05-18 16:34 ` santosh.shilimkar
2020-05-15 0:37 ` Max Gurtovoy
2020-05-14 16:00 ` Gal Pressman
2020-05-17 10:37 ` Max Gurtovoy
2020-05-18 15:20 ` Dennis Dalessandro
2020-05-18 18:10 ` Jason Gunthorpe
2020-05-19 13:43 ` Dennis Dalessandro
2020-05-19 13:53 ` Jason Gunthorpe
2020-05-19 14:19 ` Leon Romanovsky
2020-05-19 14:26 ` Dennis Dalessandro
2020-05-19 14:30 ` Jason Gunthorpe
2020-05-19 14:37 ` Dennis Dalessandro [this message]
2020-05-23 22:08 ` Jason Gunthorpe
2020-05-24 1:27 ` Tom Talpey
2020-05-26 15:38 ` Dennis Dalessandro
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=5563b8da-faf3-1af5-33d0-fe5a6d7291a1@intel.com \
--to=dennis.dalessandro@intel.com \
--cc=bvanassche@acm.org \
--cc=dledford@redhat.com \
--cc=israelr@mellanox.com \
--cc=jgg@mellanox.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=maxg@mellanox.com \
--cc=mike.marciniszyn@intel.com \
--cc=sagi@grimberg.me \
--cc=shlomin@mellanox.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).