From: Jason Gunthorpe <jgg@nvidia•com>
To: Sean Hefty <shefty@nvidia•com>
Cc: Bernard Metzler <BMT@zurich•ibm.com>,
Roland Dreier <roland@enfabrica•net>,
Nikolay Aleksandrov <nikolay@enfabrica•net>,
"netdev@vger•kernel.org" <netdev@vger•kernel.org>,
"shrijeet@enfabrica•net" <shrijeet@enfabrica•net>,
"alex.badea@keysight•com" <alex.badea@keysight•com>,
"eric.davis@broadcom•com" <eric.davis@broadcom•com>,
"rip.sohan@amd•com" <rip.sohan@amd•com>,
"dsahern@kernel•org" <dsahern@kernel•org>,
"winston.liu@keysight•com" <winston.liu@keysight•com>,
"dan.mihailescu@keysight•com" <dan.mihailescu@keysight•com>,
Kamal Heib <kheib@redhat•com>,
"parth.v.parikh@keysight•com" <parth.v.parikh@keysight•com>,
Dave Miller <davem@redhat•com>,
"ian.ziemba@hpe•com" <ian.ziemba@hpe•com>,
"andrew.tauferner@cornelisnetworks•com"
<andrew.tauferner@cornelisnetworks•com>,
"welch@hpe•com" <welch@hpe•com>,
"rakhahari.bhunia@keysight•com" <rakhahari.bhunia@keysight•com>,
"kingshuk.mandal@keysight•com" <kingshuk.mandal@keysight•com>,
"linux-rdma@vger•kernel.org" <linux-rdma@vger•kernel.org>,
"kuba@kernel•org" <kuba@kernel•org>,
Paolo Abeni <pabeni@redhat•com>
Subject: Re: [RFC PATCH 00/13] Ultra Ethernet driver introduction
Date: Wed, 26 Mar 2025 12:53:29 -0300 [thread overview]
Message-ID: <Z+Qi+XxYizfhr06P@nvidia.com> (raw)
In-Reply-To: <DM6PR12MB43137AE666F19784D2832030BDA62@DM6PR12MB4313.namprd12.prod.outlook.com>
On Wed, Mar 26, 2025 at 03:29:01PM +0000, Sean Hefty wrote:
> > > > 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?
I imagine for cases like that the job would be linked to the PD and
then MR -> PD -> Job.
The kernel side would create any HW object for the job when the PD is
created for a specific HW device.
The PD security semantic for the MR would be a little bit different in
that the PD is more like a shared PD.
Jason
next prev parent reply other threads:[~2025-03-26 15:53 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 23:01 [RFC PATCH 00/13] Ultra Ethernet driver introduction Nikolay Aleksandrov
2025-03-06 23:01 ` [RFC PATCH 01/13] drivers: ultraeth: add initial skeleton and kconfig option Nikolay Aleksandrov
2025-03-06 23:01 ` [RFC PATCH 02/13] drivers: ultraeth: add context support Nikolay Aleksandrov
2025-03-06 23:01 ` [RFC PATCH 03/13] drivers: ultraeth: add new genl family Nikolay Aleksandrov
2025-03-06 23:01 ` [RFC PATCH 04/13] drivers: ultraeth: add job support Nikolay Aleksandrov
2025-03-06 23:01 ` [RFC PATCH 05/13] drivers: ultraeth: add tunnel udp device support Nikolay Aleksandrov
2025-03-06 23:01 ` [RFC PATCH 06/13] drivers: ultraeth: add initial PDS infrastructure Nikolay Aleksandrov
2025-03-06 23:01 ` [RFC PATCH 07/13] drivers: ultraeth: add request and ack receive support Nikolay Aleksandrov
2025-03-06 23:01 ` [RFC PATCH 08/13] drivers: ultraeth: add request transmit support Nikolay Aleksandrov
2025-03-06 23:01 ` [RFC PATCH 09/13] drivers: ultraeth: add support for coalescing ack Nikolay Aleksandrov
2025-03-06 23:02 ` [RFC PATCH 10/13] drivers: ultraeth: add sack support Nikolay Aleksandrov
2025-03-06 23:02 ` [RFC PATCH 11/13] drivers: ultraeth: add nack support Nikolay Aleksandrov
2025-03-06 23:02 ` [RFC PATCH 12/13] drivers: ultraeth: add initiator and target idle timeout support Nikolay Aleksandrov
2025-03-06 23:02 ` [RFC PATCH 13/13] HACK: drivers: ultraeth: add char device Nikolay Aleksandrov
2025-03-08 18:46 ` [RFC PATCH 00/13] Ultra Ethernet driver introduction Leon Romanovsky
2025-03-09 3:21 ` Parav Pandit
2025-03-11 14:20 ` Bernard Metzler
2025-03-11 14:55 ` Leon Romanovsky
2025-03-11 17:11 ` Sean Hefty
2025-03-12 9:20 ` Nikolay Aleksandrov
2025-03-12 9:40 ` Nikolay Aleksandrov
2025-03-12 11:29 ` Leon Romanovsky
2025-03-12 14:20 ` Nikolay Aleksandrov
2025-03-12 15:10 ` Leon Romanovsky
2025-03-12 16:00 ` Nikolay Aleksandrov
2025-03-14 14:53 ` Bernard Metzler
2025-03-17 12:52 ` Leon Romanovsky
2025-03-19 13:52 ` Jason Gunthorpe
2025-03-19 14:02 ` Nikolay Aleksandrov
2025-03-14 20:51 ` Stanislav Fomichev
2025-03-17 12:30 ` Leon Romanovsky
2025-03-19 19:12 ` Stanislav Fomichev
2025-03-15 20:49 ` Netlink vs ioctl WAS(Re: " Jamal Hadi Salim
2025-03-17 12:57 ` Leon Romanovsky
2025-03-18 22:49 ` Jason Gunthorpe
2025-03-19 18:21 ` Jamal Hadi Salim
2025-03-19 19:19 ` Jason Gunthorpe
2025-03-25 14:12 ` Jamal Hadi Salim
2025-03-26 15:50 ` Jason Gunthorpe
2025-04-08 14:16 ` Jamal Hadi Salim
2025-04-09 16:10 ` Jason Gunthorpe
2025-03-19 16:48 ` Jason Gunthorpe
2025-03-20 11:13 ` Yunsheng Lin
2025-03-20 14:32 ` Jason Gunthorpe
2025-03-20 20:05 ` Sean Hefty
2025-03-20 20:12 ` Jason Gunthorpe
2025-03-21 2:02 ` Yunsheng Lin
2025-03-21 12:01 ` Jason Gunthorpe
2025-03-24 20:22 ` Roland Dreier
2025-03-24 21:28 ` Sean Hefty
2025-03-25 13:22 ` Bernard Metzler
2025-03-25 17:02 ` Sean Hefty
2025-03-26 14:45 ` Jason Gunthorpe
2025-03-26 15:29 ` Sean Hefty
2025-03-26 15:53 ` Jason Gunthorpe [this message]
2025-03-26 17:39 ` Sean Hefty
2025-03-27 13:26 ` Jason Gunthorpe
2025-03-28 12:20 ` Yunsheng Lin
2025-03-31 19:49 ` Sean Hefty
2025-04-01 9:19 ` Yunsheng Lin
2025-03-31 19:29 ` Sean Hefty
2025-04-01 13:04 ` Jason Gunthorpe
2025-04-01 16:57 ` Sean Hefty
2025-04-01 19:39 ` Jason Gunthorpe
2025-04-03 1:30 ` Sean Hefty
2025-04-04 16:03 ` Ziemba, Ian
2025-04-05 1:07 ` Sean Hefty
2025-04-07 19:32 ` Ziemba, Ian
2025-04-08 4:40 ` Sean Hefty
2025-04-16 23:58 ` Sean Hefty
2025-04-17 1:23 ` Jason Gunthorpe
2025-04-17 2:59 ` Sean Hefty
2025-04-17 13:31 ` Jason Gunthorpe
2025-04-18 16:50 ` Sean Hefty
2025-04-22 15:44 ` Jason Gunthorpe
2025-03-26 15:16 ` Jason Gunthorpe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z+Qi+XxYizfhr06P@nvidia.com \
--to=jgg@nvidia$(echo .)com \
--cc=BMT@zurich$(echo .)ibm.com \
--cc=alex.badea@keysight$(echo .)com \
--cc=andrew.tauferner@cornelisnetworks$(echo .)com \
--cc=dan.mihailescu@keysight$(echo .)com \
--cc=davem@redhat$(echo .)com \
--cc=dsahern@kernel$(echo .)org \
--cc=eric.davis@broadcom$(echo .)com \
--cc=ian.ziemba@hpe$(echo .)com \
--cc=kheib@redhat$(echo .)com \
--cc=kingshuk.mandal@keysight$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-rdma@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nikolay@enfabrica$(echo .)net \
--cc=pabeni@redhat$(echo .)com \
--cc=parth.v.parikh@keysight$(echo .)com \
--cc=rakhahari.bhunia@keysight$(echo .)com \
--cc=rip.sohan@amd$(echo .)com \
--cc=roland@enfabrica$(echo .)net \
--cc=shefty@nvidia$(echo .)com \
--cc=shrijeet@enfabrica$(echo .)net \
--cc=welch@hpe$(echo .)com \
--cc=winston.liu@keysight$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox