lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240628160027.GT2494510@nvidia.com>
Date: Fri, 28 Jun 2024 13:00:27 -0300
From: Jason Gunthorpe <jgg@...dia.com>
To: Leon Romanovsky <leon@...nel.org>
Cc: Leon Romanovsky <leonro@...dia.com>, Eric Dumazet <edumazet@...gle.com>,
	Jakub Kicinski <kuba@...nel.org>, linux-kernel@...r.kernel.org,
	linux-rdma@...r.kernel.org, Mark Zhang <markzhang@...dia.com>,
	netdev@...r.kernel.org, Paolo Abeni <pabeni@...hat.com>,
	Saeed Mahameed <saeedm@...dia.com>,
	Tariq Toukan <tariqt@...dia.com>
Subject: Re: [PATCH rdma-next 00/12] Multi-plane support for mlx5

On Sun, Jun 16, 2024 at 07:08:32PM +0300, Leon Romanovsky wrote:
> Mark Zhang (12):
>   RDMA/core: Create "issm*" device nodes only when SMI is supported
>   net/mlx5: mlx5_ifc update for multi-plane support
>   RDMA/mlx5: Add support to multi-plane device and port
>   RDMA/core: Support IB sub device with type "SMI"
>   RDMA: Set type of rdma_ah to IB for a SMI sub device
>   RDMA/core: Create GSI QP only when CM is supported
>   RDMA/mlx5: Support plane device and driver APIs to add and delete it
>   RDMA/nldev: Add support to add/delete a sub IB device through netlink
>   RDMA/nldev: Add support to dump device type and parent device if
>     exists
>   RDMA/mlx5: Add plane index support when querying PTYS registers
>   net/mlx5: mlx5_ifc update for accessing ppcnt register of plane ports
>   RDMA/mlx5: Support per-plane port IB counters by querying PPCNT
>     register

This all seems quite straightforward, Leon are you going to put this
on a shared branch with all the IFC stuff/etc?

Thanks,
Jason

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ