Sat, Dec 30, 2017 at 11:18:50AM CET, and...@lunn.ch wrote: >> 1. Both dpipe and devlink resource are abstraction models for >> hardware entities, and as a result they true to provide generic objects. >> Each driver/ASIC should register his own and it absolutely proprietary >> implementation. There is absolutely NO industry standard here, the only >> thing that resembles a standard is that dpipe looks a bit like P4 only >> because its proved to be useful for describing packet forwarding >> pipelines. The host4 table is just a hardware process in the mellanox >> spectrum ASIC pipeline and it should not be part of ABI, sorry I clearly >> don't understand how this even came up. > >Why should it not be part of the ABI? Are you saying it will change >from version to version? Are you trying to warning people not to write >scripts using it, because its meaning will change and what works now >will break in the next kernel version?
In my opinion it should not change. Unless there is a bug (like the one DaveA found in mlxsw erif table). Existing tables and resources should be only added. It is the driver's maintainer responsibility to not to break user scripts.
