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:
 <DM6PR12MB43137AE666F19784D2832030BDA62@DM6PR12MB4313.namprd12.prod.outlook.com>
Date: Wed, 26 Mar 2025 15:29:01 +0000
From: Sean Hefty <shefty@...dia.com>
To: Jason Gunthorpe <jgg@...dia.com>
CC: Bernard Metzler <BMT@...ich.ibm.com>, Roland Dreier
	<roland@...abrica.net>, 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>, "winston.liu@...sight.com"
	<winston.liu@...sight.com>, "dan.mihailescu@...sight.com"
	<dan.mihailescu@...sight.com>, Kamal Heib <kheib@...hat.com>,
	"parth.v.parikh@...sight.com" <parth.v.parikh@...sight.com>, Dave Miller
	<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>, Paolo Abeni <pabeni@...hat.com>
Subject: RE: [RFC PATCH 00/13] Ultra Ethernet driver introduction

> > > If I understand UEC's job semantics correctly, then the local scope
> > > of a job may span multiple local ports from multiple local devices.
> > > It would of course translate into device specific reservations.
> >
> > Agreed.  I should have said job id/address has a network address
> > scope.  For example, job 3 at 10.0.0.1 _may_ be a different logical
> > job than job 3 at 10.0.0.2.  Or they could also belong to the same
> > logical job.  Or the same logical job may use different job id values
> > for different network addresses.
> >
> > A device-centric model is more aligned with the RDMA stack.  IMO,
> > higher-level SW would then be responsible for configuring and managing
> > the logical job.  For example, maybe it needs to assign and configure
> > non-RDMA resources as well.  For that reason, I would push the logical
> > job management outside the kernel subsystem.
> 
> Like I said already, I think Job needs to be a first class RDMA object that is used
> by all transports that have job semantics.

How do you handle or expose device specific resource allocations or restrictions, which may be needed?  Should a kernel 'RDMA job manager' abstract device level resources?

Consider a situation where a MR or MW should only be accessible by a specific job.  When the MR is created, the device specific job resource may be needed.  Should drivers need to query the job manager to map some global object to a device specific resource?

Other than this difference, I agree with the other points.

- Sean