[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241104082710.GB99170@unreal>
Date: Mon, 4 Nov 2024 10:27:10 +0200
From: Leon Romanovsky <leon@...nel.org>
To: Jakub Kicinski <kuba@...nel.org>, Jason Gunthorpe <jgg@...dia.com>
Cc: Edward Srouji <edwards@...dia.com>, linux-kernel@...r.kernel.org,
linux-rdma@...r.kernel.org, netdev@...r.kernel.org,
Saeed Mahameed <saeedm@...dia.com>,
Tariq Toukan <tariqt@...dia.com>, Yishai Hadas <yishaih@...dia.com>
Subject: Re: [PATCH rdma-next 0/2] Introduce mlx5 data direct placement (DDP)
On Tue, Sep 03, 2024 at 02:37:50PM +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@...dia.com>
>
> Hi,
>
> This series from Edward introduces mlx5 data direct placement (DDP)
> feature.
>
> This feature allows WRs on the receiver side of the QP to be consumed
> out of order, permitting the sender side to transmit messages without
> guaranteeing arrival order on the receiver side.
>
> When enabled, the completion ordering of WRs remains in-order,
> regardless of the Receive WRs consumption order.
>
> RDMA Read and RDMA Atomic operations on the responder side continue to
> be executed in-order, while the ordering of data placement for RDMA
> Write and Send operations is not guaranteed.
>
> Thanks
>
> Edward Srouji (2):
> net/mlx5: Introduce data placement ordering bits
Jakub,
We applied this series to RDMA and first patch generates merge conflicts
in include/linux/mlx5/mlx5_ifc.h between netdev and RDMA trees.
Can you please pull shared mlx5-next branch to avoid it?
Thanks
> RDMA/mlx5: Support OOO RX WQE consumption
>
> drivers/infiniband/hw/mlx5/main.c | 8 +++++
> drivers/infiniband/hw/mlx5/mlx5_ib.h | 1 +
> drivers/infiniband/hw/mlx5/qp.c | 51 +++++++++++++++++++++++++---
> include/linux/mlx5/mlx5_ifc.h | 24 +++++++++----
> include/uapi/rdma/mlx5-abi.h | 5 +++
> 5 files changed, 78 insertions(+), 11 deletions(-)
>
> --
> 2.46.0
>
>
Powered by blists - more mailing lists