From: Christoph Hellwig <hch@infradead.org>
To: Sagi Grimberg <sagigrim@gmail.com>
Cc: Alexey Lyashkov <umka@cloudlinux.com>,
Max Gurtovoy <maxg@mellanox.com>,
Bart Van Assche <bvanassche@acm.org>,
Leon Romanovsky <leon@kernel.org>,
Israel Rukshin <israelr@mellanox.com>,
sagi@grimberg.me, jgg@mellanox.com, linux-rdma@vger.kernel.org,
dledford@redhat.com, sergeygo@mellanox.com
Subject: Re: [PATCH] IB/iser: Remove support for FMR memory registration
Date: Mon, 18 May 2020 00:16:24 -0700 [thread overview]
Message-ID: <20200518071624.GA20312@infradead.org> (raw)
In-Reply-To: <9fe7ac28-4702-d537-a568-c3eb0b5b0ce3@gmail.com>
On Sun, May 17, 2020 at 01:35:33AM -0700, Sagi Grimberg wrote:
>
>
> On 5/14/20 3:09 AM, Alexey Lyashkov wrote:
> > CX3 with fast registration isn’t stable enough.
> > I was make this change for Lustre for year or two ago, but it was
> > reverted by serious bugs.
>
> This must be issues with the Lustre implementation, all the rest of the ULPs
> (almost) default
> to FRWR.
And even if it wasn't out of tree junk like Lustre simply doesn't matter
for upstream decisions.
next prev parent reply other threads:[~2020-05-18 7:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 16:08 [PATCH] IB/iser: Remove support for FMR memory registration Israel Rukshin
2020-05-12 17:16 ` Leon Romanovsky
2020-05-12 17:53 ` Max Gurtovoy
2020-05-12 20:09 ` Bart Van Assche
2020-05-12 20:13 ` Jason Gunthorpe
2020-05-12 20:27 ` Bart Van Assche
2020-05-12 23:06 ` Jason Gunthorpe
2020-05-13 0:53 ` Sagi Grimberg
2020-05-13 7:18 ` Leon Romanovsky
2020-05-13 16:44 ` Dennis Dalessandro
2020-05-13 18:43 ` Leon Romanovsky
2020-05-13 19:49 ` Bart Van Assche
2020-05-13 8:43 ` Max Gurtovoy
2020-05-13 11:29 ` Tom Talpey
[not found] ` <0C22D41B-89CD-4B2D-B514-8EA06F2233D7@cloudlinux.com>
2020-05-14 10:50 ` Max Gurtovoy
2020-05-14 13:50 ` Tom Talpey
2020-05-17 8:35 ` Sagi Grimberg
2020-05-17 14:55 ` Alexey Lyashkov
2020-05-18 7:16 ` Christoph Hellwig [this message]
2020-05-13 0:56 ` Sagi Grimberg
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=20200518071624.GA20312@infradead.org \
--to=hch@infradead.org \
--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=sagi@grimberg.me \
--cc=sagigrim@gmail.com \
--cc=sergeygo@mellanox.com \
--cc=umka@cloudlinux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.