From: Florian Fainelli <f.fainelli@xxxxxxxxx> Date: Thu, 12 Oct 2017 08:43:59 -0700 > Once we move ethtool (or however we name its successor) over to > netlink there is an opportunity for accessing objects that do and do > not have a netdevice representor today (e.g: management ports on > switches) with the same interface, and devlink could be used for > that. That is an interesting angle for including this in devlink. I'm not so sure what to do about this. One suggestion is that devlink is used for getting ethtool stats for objects lacking netdev representor's, and a new genetlink family is used for netdev based ethtool. I think it's important that we don't expand the scope of devlink beyond what it was originally designed for.
