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

Sean Hefty
2025-03-25T17:02:41Z

> > 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