[...]
Just to elaborate...
Any application using lldp information will want to get events when
TLVs change. Maybe you can contrive ethtool to do this but its going to
be ugly. Netlink can support multicast events and applications can
register for them. Also netlink's TLV format matches nicely with LLDPs
TLV format.
ethtool and netlink usually intersect for a few bits of information
such as link status for instance. It is useful to have this
information twice, with ethtool as a debugging aid, and via netlink to
take appropriate actions.
Maybe we just need to be clear on what needs to be present in ethtool
only (configuration, static information) and see on a case-by-case
what needs to be present in both ethtool and netlink?
OK if there is an enable/disable bit in ethtool that might make some
sense. Or an error flag that is helpful to have.
In this case we are dealing with peer attributes which are dynamic and
in my opinion should go into netlink and duplicating them in ethtool
although possible doesn't seem very useful to me.
.John
--
To unsubscribe from this list: send the line "unsubscribe linux-s390" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
