From: Jason Gunthorpe <jgg@ziepe.ca>
To: santosh.shilimkar@oracle.com
Cc: linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
aron.silverton@oracle.com, Max Gurtovoy <maxg@mellanox.com>,
oren@mellanox.com, shlomin@mellanox.com, vladimirk@mellanox.com
Subject: Re: [PATCH v3 03/13] RDMA/rds: Remove FMR support for memory registration
Date: Fri, 29 May 2020 16:12:48 -0300 [thread overview]
Message-ID: <20200529191248.GB21651@ziepe.ca> (raw)
In-Reply-To: <27824c0c-06ba-40dd-34c2-2888fe8db5c8@oracle.com>
On Thu, May 28, 2020 at 01:21:33PM -0700, santosh.shilimkar@oracle.com wrote:
> On 5/28/20 12:45 PM, Jason Gunthorpe wrote:
> > From: Max Gurtovoy <maxg@mellanox.com>
> >
> > Use FRWR method for memory registration by default and remove the ancient
> > and unsafe FMR method.
> >
> > Signed-off-by: Max Gurtovoy <maxg@mellanox.com>
> > Signed-off-by: Jason Gunthorpe <jgg@mellanox.com>
>
> > net/rds/Makefile | 2 +-
> > net/rds/ib.c | 20 ++--
> > net/rds/ib.h | 2 -
> > net/rds/ib_cm.c | 4 +-
> > net/rds/ib_fmr.c | 269 ----------------------------------------------
> > net/rds/ib_frmr.c | 4 +-
> > net/rds/ib_mr.h | 14 +--
> > net/rds/ib_rdma.c | 28 ++---
> > 8 files changed, 21 insertions(+), 322 deletions(-)
> > delete mode 100644 net/rds/ib_fmr.c
> >
> Patch looks accurate to me Jason/Max. I wanted to get few regression
> tests run with it before providing the ack. Will send a note once
> its tested ok.
Okay, since we are at the merge window I'm going to put it in
linux-next to look for build regressions with the idea to send it on
Thursday
Thanks,
Jason
next prev parent reply other threads:[~2020-05-29 19:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 19:45 [PATCH v3 00/13] Remove FMR support from RDMA drivers Jason Gunthorpe
2020-05-28 19:45 ` [PATCH v3 01/13] RDMA/iser: Remove support for FMR memory registration Jason Gunthorpe
2020-05-28 19:45 ` [PATCH v3 02/13] RDMA/srp: " Jason Gunthorpe
2020-05-28 19:45 ` [PATCH v3 03/13] RDMA/rds: Remove FMR support for " Jason Gunthorpe
2020-05-28 20:21 ` santosh.shilimkar
2020-05-29 19:12 ` Jason Gunthorpe [this message]
2020-06-16 2:33 ` santosh.shilimkar
2020-05-28 19:45 ` [PATCH v3 04/13] RDMA/core: Remove FMR pool API Jason Gunthorpe
2020-05-28 19:45 ` [PATCH v3 05/13] RDMA/mlx5: Remove FMR leftovers Jason Gunthorpe
2020-05-28 19:45 ` [PATCH v3 06/13] RDMA/bnxt_re: " Jason Gunthorpe
2020-05-28 19:45 ` [PATCH v3 07/13] RDMA/i40iw: " Jason Gunthorpe
2020-05-29 15:20 ` Saleem, Shiraz
2020-05-28 19:45 ` [PATCH v3 08/13] RDMA/mlx4: Remove FMR support for memory registration Jason Gunthorpe
2020-05-28 19:45 ` [PATCH v3 09/13] RDMA/mthca: " Jason Gunthorpe
2020-05-28 19:45 ` [PATCH v3 10/13] RDMA/rdmavt: Remove FMR " Jason Gunthorpe
2020-05-28 19:45 ` [PATCH v3 11/13] RDMA/core: Remove FMR device ops Jason Gunthorpe
2020-05-28 19:45 ` [PATCH v3 12/13] RDMA: Remove 'max_fmr' Jason Gunthorpe
2020-05-29 14:54 ` Bernard Metzler
2020-05-28 19:45 ` [PATCH v3 13/13] RDMA: Remove 'max_map_per_fmr' Jason Gunthorpe
2020-05-29 19:17 ` [PATCH v3 00/13] Remove FMR support from RDMA drivers Jason Gunthorpe
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=20200529191248.GB21651@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=aron.silverton@oracle.com \
--cc=linux-rdma@vger.kernel.org \
--cc=maxg@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=oren@mellanox.com \
--cc=santosh.shilimkar@oracle.com \
--cc=shlomin@mellanox.com \
--cc=vladimirk@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).