Re: [PATCH v6 2/2] mctp pcc: Implement MCTP over PCC Transport

From: Adam Young
Date: Tue Nov 05 2024 - 15:16:39 EST



On 11/1/24 04:55, Jeremy Kerr wrote:
Just to clarify that: for physical (ie, null-EID) addressing, you don't
need the hardware address, you need:

1) the outgoing interface's ifindex; and
2) the hardware address of the*remote* endpoint, in whatever
format is appropriate for link type


So Here is what I was thinking:

Lets ignore the namespace for now, as that is a future-proofing thing and will be all 0.  If The OS listens on index 11 and the PLatform listens index 22, the HW address for the OS would be

00001122

and for the Platform

00002211

This is all the info  for the calling application to know both the ifindex and the remote endpoint.

They can re-order the address to 00002211 for the remote endpoint.  If they have the link they have the ifindex.  It seems like a clean solution.

Adding the inbox id ( to the HW address does not harm anything, and it makes things much more explicit.

It seems like removing either the inbox or the outbox id from the HW address is hiding information that should be exposed.  And the two together make up the hardware addressing for the device, just not in that exact format, but it maps directly.  That is what will be in the upcoming version of the spec as well.