Re: [RFC PATCH net-next 0/2] Add new switchdev device class

[Andrew Lunn <andrew@lunn.ch>]

> I don't know about how this overlaps with DSA platform_class.  Florian?

There is some overlap with DSA, but the current DSA model, with
respect to probing, is broken. So this might be interesting as a way
towards fix that.

One thing to keep in mind is the D in DSA. You talk about switch,
singular. DSA has a number of switches in a cluster. We currently
export a single switchdev interface for the cluster, but there are
some properties which are per switch, e.g. temperature, eeprom
contents, statistics, power management etc.


Although ethtool does have options for these, it is not always a
natural fit. ethtool --eeprom-dump on a switch port dumps the switch
EEPROM, and all ports on the switch can be used. --register-dump on a
port is good for showing the per ports registers, but there is no
natural interface for showing the global switch registers. Florian's
resent L2 interface patch shows we have issues getting access to the
'cpu' port, the port which interfaces to the host.

We need to be careful that any new interfaces we add are better at
representing the true structure of the hardware, which includes there
being multiple physical switches below a switchdev, and they are
connected together by ports which are currently not visible as
netdevs.

      Andrew