Netdev List
 help / color / mirror / Atom feed
* Re: (subset) [PATCH rdma-next 0/2] Introduce mlx5 data direct placement (DDP)
       [not found] <cover.1725362773.git.leon@kernel.org>
@ 2024-11-04  8:20 ` Leon Romanovsky
  2024-11-04  8:27 ` Leon Romanovsky
  1 sibling, 0 replies; 4+ messages in thread
From: Leon Romanovsky @ 2024-11-04  8:20 UTC (permalink / raw)
  To: Jason Gunthorpe, Leon Romanovsky
  Cc: Edward Srouji, linux-kernel, linux-rdma, netdev, Saeed Mahameed,
	Tariq Toukan, Yishai Hadas, Leon Romanovsky


On Tue, 03 Sep 2024 14:37:50 +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
> 
> Hi,
> 
> This series from Edward introduces mlx5 data direct placement (DDP)
> feature.
> 
> [...]

Applied, thanks!

[2/2] RDMA/mlx5: Support OOO RX WQE consumption
      https://git.kernel.org/rdma/rdma/c/ded397366b5540

Best regards,
-- 
Leon Romanovsky <leon@kernel.org>


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH rdma-next 0/2] Introduce mlx5 data direct placement (DDP)
       [not found] <cover.1725362773.git.leon@kernel.org>
  2024-11-04  8:20 ` (subset) [PATCH rdma-next 0/2] Introduce mlx5 data direct placement (DDP) Leon Romanovsky
@ 2024-11-04  8:27 ` Leon Romanovsky
  2024-11-05  2:53   ` Jakub Kicinski
  1 sibling, 1 reply; 4+ messages in thread
From: Leon Romanovsky @ 2024-11-04  8:27 UTC (permalink / raw)
  To: Jakub Kicinski, Jason Gunthorpe
  Cc: Edward Srouji, linux-kernel, linux-rdma, netdev, Saeed Mahameed,
	Tariq Toukan, Yishai Hadas

On Tue, Sep 03, 2024 at 02:37:50PM +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.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
> 
> 

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH rdma-next 0/2] Introduce mlx5 data direct placement (DDP)
  2024-11-04  8:27 ` Leon Romanovsky
@ 2024-11-05  2:53   ` Jakub Kicinski
  2024-11-05  6:26     ` Leon Romanovsky
  0 siblings, 1 reply; 4+ messages in thread
From: Jakub Kicinski @ 2024-11-05  2:53 UTC (permalink / raw)
  To: Leon Romanovsky
  Cc: Jason Gunthorpe, Edward Srouji, linux-kernel, linux-rdma, netdev,
	Saeed Mahameed, Tariq Toukan, Yishai Hadas

On Mon, 4 Nov 2024 10:27:10 +0200 Leon Romanovsky wrote:
> 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?

Sorry I don't have the context, the thread looks 2 months old.
If you'd like us to pull something please sense a pull request
targeting net-next...

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [PATCH rdma-next 0/2] Introduce mlx5 data direct placement (DDP)
  2024-11-05  2:53   ` Jakub Kicinski
@ 2024-11-05  6:26     ` Leon Romanovsky
  0 siblings, 0 replies; 4+ messages in thread
From: Leon Romanovsky @ 2024-11-05  6:26 UTC (permalink / raw)
  To: Jakub Kicinski
  Cc: Jason Gunthorpe, Edward Srouji, linux-kernel, linux-rdma, netdev,
	Saeed Mahameed, Tariq Toukan, Yishai Hadas

On Mon, Nov 04, 2024 at 06:53:03PM -0800, Jakub Kicinski wrote:
> On Mon, 4 Nov 2024 10:27:10 +0200 Leon Romanovsky wrote:
> > 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?
> 
> Sorry I don't have the context, the thread looks 2 months old.
> If you'd like us to pull something please sense a pull request
> targeting net-next...

Sure, will do.

Thanks

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2024-11-05  6:26 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <cover.1725362773.git.leon@kernel.org>
2024-11-04  8:20 ` (subset) [PATCH rdma-next 0/2] Introduce mlx5 data direct placement (DDP) Leon Romanovsky
2024-11-04  8:27 ` Leon Romanovsky
2024-11-05  2:53   ` Jakub Kicinski
2024-11-05  6:26     ` Leon Romanovsky

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox