netdev - RE: [RFC PATCH 00/13] Ultra Ethernet driver introduction

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:
 <DM6PR12MB43132490CF7D1CC16AF6D42CBDD82@DM6PR12MB4313.namprd12.prod.outlook.com>
Date: Thu, 20 Mar 2025 20:05:05 +0000
From: Sean Hefty <shefty@...dia.com>
To: Jason Gunthorpe <jgg@...dia.com>, Yunsheng Lin <linyunsheng@...wei.com>
CC: Nikolay Aleksandrov <nikolay@...abrica.net>, "netdev@...r.kernel.org"
	<netdev@...r.kernel.org>, "shrijeet@...abrica.net" <shrijeet@...abrica.net>,
	"alex.badea@...sight.com" <alex.badea@...sight.com>,
	"eric.davis@...adcom.com" <eric.davis@...adcom.com>, "rip.sohan@....com"
	<rip.sohan@....com>, "dsahern@...nel.org" <dsahern@...nel.org>,
	"bmt@...ich.ibm.com" <bmt@...ich.ibm.com>, "roland@...abrica.net"
	<roland@...abrica.net>, "winston.liu@...sight.com"
	<winston.liu@...sight.com>, "dan.mihailescu@...sight.com"
	<dan.mihailescu@...sight.com>, "kheib@...hat.com" <kheib@...hat.com>,
	"parth.v.parikh@...sight.com" <parth.v.parikh@...sight.com>,
	"davem@...hat.com" <davem@...hat.com>, "ian.ziemba@....com"
	<ian.ziemba@....com>, "andrew.tauferner@...nelisnetworks.com"
	<andrew.tauferner@...nelisnetworks.com>, "welch@....com" <welch@....com>,
	"rakhahari.bhunia@...sight.com" <rakhahari.bhunia@...sight.com>,
	"kingshuk.mandal@...sight.com" <kingshuk.mandal@...sight.com>,
	"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>, "kuba@...nel.org"
	<kuba@...nel.org>, "pabeni@...hat.com" <pabeni@...hat.com>, huchunzhi
	<huchunzhi@...wei.com>, "jerry.lilijun@...wei.com"
	<jerry.lilijun@...wei.com>, "zhangkun09@...wei.com" <zhangkun09@...wei.com>,
	"wang.chihyung@...wei.com" <wang.chihyung@...wei.com>
Subject: RE: [RFC PATCH 00/13] Ultra Ethernet driver introduction

> > As the existing rdma subsystem doesn't seems to support the above use
> > case yet
> 
> Why would you say that? If EFA needs SRD and RDM objects in RDMA they
> can create them, it is not a big issue. To my knowledge they haven't asked for
> them.

When looking at how to integrate UET support into verbs, there were changes relevant to this discussion that I found needed.

1. Allow an RDMA device to indicate that it supports multiple transports, separated per port.
2. Specify the QP type separate from the protocol.
3. Define a reliable, unconnected QP type.

Lin might be referring to 2 (assuming 3 is resolved).

These are straightforward to address.  I don't think we'd end up with a protocol object (e.g. SRD), versus it just being an attribute of 3 (e.g. RDM QP).

EFA defined a custom QP type with a single protocol, so they didn't try to standardize this.  However, it could fit into the above model.

- Sean