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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID:
 <DM6PR12MB431329322A0C0CCB7D5F85E6BDA72@DM6PR12MB4313.namprd12.prod.outlook.com>
Date: Tue, 25 Mar 2025 17:02:37 +0000
From: Sean Hefty <shefty@...dia.com>
To: Bernard Metzler <BMT@...ich.ibm.com>, Roland Dreier
	<roland@...abrica.net>, Jason Gunthorpe <jgg@...dia.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>,
	"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

> > I view a job as scoped by a network address, versus a system global object.
> > So, I was looking at a per device scope, though I guess a per port
> > (similar to a pkey) is also possible.  My reasoning was that a device
> > _may_ need to allocate some per job resource.  Per device job objects
> > could be configured to have the same 'job address', for an indirect association.
> >
> 
> 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.

- Sean