From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Christoph Hellwig <hch@lst.de>,
Doug Ledford <dledford@redhat.com>,
Avihai Horon <avihaih@nvidia.com>,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
Bart Van Assche <bvanassche@acm.org>, Tom Talpey <tom@talpey.com>,
Santosh Shilimkar <santosh.shilimkar@oracle.com>,
Chuck Lever III <chuck.lever@oracle.com>,
Keith Busch <kbusch@kernel.org>,
David Laight <David.Laight@aculab.com>,
Honggang LI <honli@redhat.com>,
Max Gurtovoy <mgurtovoy@nvidia.com>
Subject: Re: [PATCH v2 rdma-next] RDMA/mlx5: Enable Relaxed Ordering by default for kernel ULPs
Date: Tue, 22 Jun 2021 09:20:21 +0300 [thread overview]
Message-ID: <YNGBJRRWBql413nM@unreal> (raw)
In-Reply-To: <20210621231837.GT1002214@nvidia.com>
On Mon, Jun 21, 2021 at 08:18:37PM -0300, Jason Gunthorpe wrote:
> On Mon, Jun 21, 2021 at 10:20:33PM +0200, Christoph Hellwig wrote:
> > On Mon, Jun 21, 2021 at 03:02:05PM -0300, Jason Gunthorpe wrote:
> > > Someone is working on dis-entangling the access flags? It took a long
> > > time to sort out that this mess in wr.c actually does have a
> > > distinct user/kernel call chain too..
> >
> > I'd love to see it done, but I won't find time for it anytime soon.
>
> Heh, me too..
>
> I did actually once try to get a start on doing something to wr.c but
> it rapidly started to get into mire..
>
> I thought I recalled Leon saying he or Avihai would work on the ACCESS
> thing anyhow?
Yes, we are planning to do it for the next cycle.
Thanks
>
> Thanks,
> Jason
next prev parent reply other threads:[~2021-06-22 6:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 11:05 [PATCH v2 rdma-next] RDMA/mlx5: Enable Relaxed Ordering by default for kernel ULPs Leon Romanovsky
2021-06-09 12:52 ` Christoph Hellwig
2021-06-09 13:53 ` Leon Romanovsky
2021-06-09 13:59 ` Christoph Hellwig
2021-06-10 7:44 ` Leon Romanovsky
2021-06-09 14:10 ` David Laight
2021-06-09 14:37 ` Chuck Lever III
2021-06-09 15:05 ` David Laight
2021-06-09 15:09 ` Jason Gunthorpe
2021-06-09 15:48 ` David Laight
2021-06-21 18:02 ` Jason Gunthorpe
2021-06-21 20:20 ` Christoph Hellwig
2021-06-21 23:18 ` Jason Gunthorpe
2021-06-22 6:20 ` Leon Romanovsky [this message]
2021-06-23 23:06 ` Max Gurtovoy
2021-06-24 6:38 ` Leon Romanovsky
2021-06-24 7:39 ` Max Gurtovoy
2021-06-24 11:36 ` Jason Gunthorpe
2021-06-27 7:32 ` Leon Romanovsky
2021-06-27 7:30 ` Leon Romanovsky
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=YNGBJRRWBql413nM@unreal \
--to=leon@kernel.org \
--cc=David.Laight@aculab.com \
--cc=avihaih@nvidia.com \
--cc=bvanassche@acm.org \
--cc=chuck.lever@oracle.com \
--cc=dledford@redhat.com \
--cc=hch@lst.de \
--cc=honli@redhat.com \
--cc=jgg@nvidia.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mgurtovoy@nvidia.com \
--cc=santosh.shilimkar@oracle.com \
--cc=tom@talpey.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.