From: Jason Gunthorpe <jgg@ziepe.ca>
To: Yishai Hadas <yishaih@mellanox.com>
Cc: linux-rdma@vger.kernel.org, dledford@redhat.com,
saeedm@mellanox.com, maorg@mellanox.com, michaelgur@mellanox.com,
netdev@vger.kernel.org
Subject: Re: [PATCH rdma-next 00/10] Relaxed ordering memory regions
Date: Wed, 15 Jan 2020 14:08:48 -0400 [thread overview]
Message-ID: <20200115180848.GA13397@ziepe.ca> (raw)
In-Reply-To: <1578506740-22188-1-git-send-email-yishaih@mellanox.com>
On Wed, Jan 08, 2020 at 08:05:30PM +0200, Yishai Hadas wrote:
> This series adds an ioctl command to allocate an async event file followed by a
> new ioctl command to get a device context.
>
> The get device context command enables reading some core generic capabilities
> such as supporting an optional MR access flags by IB core and its related
> drivers.
>
> Once the above is enabled, a new optional MR access flag named
> IB_UVERBS_ACCESS_RELAXED_ORDERING is added and is used by mlx5 driver.
>
> This optional flag allows creation of relaxed ordering memory regions. Access
> through such MRs can improve performance by allowing the system to reorder
> certain accesses.
>
> As relaxed ordering is an optimization, drivers that do not support it can
> simply ignore it.
>
> Note: This series relies on the 'Refactoring FD usage' series [1] that was sent
> to rdma-next.
> [1] https://patchwork.kernel.org/project/linux-rdma/list/?series=225541
>
> Yishai
>
> Jason Gunthorpe (3):
> RDMA/core: Add UVERBS_METHOD_ASYNC_EVENT_ALLOC
> RDMA/core: Remove ucontext_lock from the uverbs_destry_ufile_hw() path
> RDMA/uverbs: Add ioctl command to get a device context
>
> Michael Guralnik (7):
> net/mlx5: Expose relaxed ordering bits
> RDMA/uverbs: Verify MR access flags
> RDMA/core: Add optional access flags range
> RDMA/efa: Allow passing of optional access flags for MR registration
> RDMA/uverbs: Add new relaxed ordering memory region access flag
> RDMA/core: Add the core support field to METHOD_GET_CONTEXT
> RDMA/mlx5: Set relaxed ordering when requested
This looks OK, can you update the shared branch please
Thanks,
Jason
next prev parent reply other threads:[~2020-01-15 18:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 18:05 [PATCH rdma-next 00/10] Relaxed ordering memory regions Yishai Hadas
2020-01-08 18:05 ` [PATCH rdma-next 01/10] net/mlx5: Expose relaxed ordering bits Yishai Hadas
2020-01-08 18:05 ` [PATCH rdma-next 02/10] RDMA/core: Add UVERBS_METHOD_ASYNC_EVENT_ALLOC Yishai Hadas
2020-01-08 18:05 ` [PATCH rdma-next 03/10] RDMA/core: Remove ucontext_lock from the uverbs_destry_ufile_hw() path Yishai Hadas
2020-01-08 18:05 ` [PATCH rdma-next 04/10] RDMA/uverbs: Add ioctl command to get a device context Yishai Hadas
2020-01-08 18:05 ` [PATCH rdma-next 05/10] RDMA/uverbs: Verify MR access flags Yishai Hadas
2020-01-08 18:05 ` [PATCH rdma-next 06/10] RDMA/core: Add optional access flags range Yishai Hadas
2020-01-08 18:05 ` [PATCH rdma-next 07/10] RDMA/efa: Allow passing of optional access flags for MR registration Yishai Hadas
2020-01-21 16:37 ` Gal Pressman
2020-01-21 16:57 ` Yishai Hadas
2020-01-22 7:51 ` Gal Pressman
2020-01-08 18:05 ` [PATCH rdma-next 08/10] RDMA/uverbs: Add new relaxed ordering memory region access flag Yishai Hadas
2020-01-09 9:38 ` Sergei Shtylyov
2020-01-15 18:05 ` Jason Gunthorpe
2020-01-08 18:05 ` [PATCH rdma-next 09/10] RDMA/core: Add the core support field to METHOD_GET_CONTEXT Yishai Hadas
2020-01-08 18:05 ` [PATCH rdma-next 10/10] RDMA/mlx5: Set relaxed ordering when requested Yishai Hadas
2020-01-15 18:08 ` Jason Gunthorpe [this message]
2020-01-16 9:20 ` [PATCH rdma-next 00/10] Relaxed ordering memory regions Leon Romanovsky
2020-01-16 20:11 ` 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=20200115180848.GA13397@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=dledford@redhat.com \
--cc=linux-rdma@vger.kernel.org \
--cc=maorg@mellanox.com \
--cc=michaelgur@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.com \
--cc=yishaih@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).