Post by nschellenberger on May 10, 2023 22:15:22 GMT
Silly question: is there any standard guidance concerning how/where to expose the PCIe bus number of the B/D/F for a device?
Anecdotally, it looks as though different vendors have historically done things in different ways. Dell iDRAC seems to prefer encoding it in the Id property as "B-D" solely by convention (as opposed to by schema metadata) e.g. "27-0" being bus 27, device 0. HPE iLO seems to use an HP Oem extension(s) with the bus number as a property.
In our case, we have a fabric-y situation where the bus numbers can actually change over time and my gut tells me encoding it in the Id is going to cause headaches for us down the road if the Ids are not invariant across time.... OTOH an Oem extension is, well, an extension. Even if there is no formal requirement or specification, if things have effectively gravitated to some sort of informal consensus, I'm happy to follow that.
Anecdotally, it looks as though different vendors have historically done things in different ways. Dell iDRAC seems to prefer encoding it in the Id property as "B-D" solely by convention (as opposed to by schema metadata) e.g. "27-0" being bus 27, device 0. HPE iLO seems to use an HP Oem extension(s) with the bus number as a property.
In our case, we have a fabric-y situation where the bus numbers can actually change over time and my gut tells me encoding it in the Id is going to cause headaches for us down the road if the Ids are not invariant across time.... OTOH an Oem extension is, well, an extension. Even if there is no formal requirement or specification, if things have effectively gravitated to some sort of informal consensus, I'm happy to follow that.
