[PATCH net-next] net: mctp: Expose transport binding identifier via IFLA attribute

[Jeremy Kerr]

Hi Jakub,

> > However, we currently have no means to get this information from
> > MCTP links.
> 
> I'm not opposed to the netlink attribute, but to be clear this info 
> is indirectly available in sysfs, right? We link the netdev to 
> the parent device so the type of /sys/class/net/$your_ifc/device
> should reveal what the transport is?

It's likely derivable from the parent device, but requires some
heuristics in userspace to map this to a transport type.

Having a well-defined place to provide the DMTF-specified transport
identifier makes this a little more straightforward to determine which
spec we're dealing with, for any transport-specific behaviour. For
example, some bus types require endpoints to announce their presence,
others do not.

Cheers,


Jeremy