On 09/22/14 21:36, John Fastabend wrote:
n-tuple has some deficiencies,- its not possible to get the capabilities to learn what fields are supported by the device, what actions, etc. - its ioctl based so we have to poll the device - only supports a single table, where we have devices with multiple tables - sort of the same as above but it doesn't allow creating new tables or destroying old tables. I probably missed a few others
A few more I can think of which are generic: The whole event subsystem allowing multi-user sync or monitoring offered by netlink is missing because ethtool ioctl go directly to the driver. The synchronous interface vs async offered by netlink offers a more effective user programmability. The ioctl binary interface whose extensibility is a pain (dont let Stephen H hear you mention ioctls for just this one reason).
but those are the main ones that I would like to address. Granted other than the ioctl line the rest could be solved by extending the existing interface. However I would just assume port it to ndo_ops and netlink then extend the existing ioctl seeing it needs a reasonable overall to support the above anyways. We could port the ethtool ops over to the new interface to simplify drivers.
Indeed. cheers, jamal
.John
_______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
