I think the netlink API and job handling overall is the area where the most
discussion is probably required. UE is somewhat novel in elevating the concept
of a "job" to a standard object with specific properties that determine the
values in packet headers. But I'm open to making "job" a top-level RDMA
object... I guess the idea would be to define an interface for creating a new
type of "job FD" with a standard ABI for setting properties?

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.

I considered using an fd to share a job object between processes; however, sharing was restricted per device.

I believe a job may be associated with other security objects (e.g. encryption) which may also need per device allocations and state tracking.

- Sean