From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jamal Hadi Salim Subject: Re: [patch net-next v2 8/9] switchdev: introduce Netlink API Date: Tue, 23 Sep 2014 07:09:10 -0400 Message-ID: <542154D6.3050406@mojatatu.com> References: <20140919154946.GH1980@nanopsycho.orion> <541C6E6D.9000109@mojatatu.com> <541CAA3C.5080105@intel.com> <20140920081426.GE1821@nanopsycho.orion> <20140920105354.GA29419@casper.infradead.org> <20140922081341.GA20905@casper.infradead.org> <20140922221727.GA4708@casper.infradead.org> <20140922225305.GB4708@casper.infradead.org> <5420CEAC.2070104@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Thomas Graf , Alexei Starovoitov , Jiri Pirko , John Fastabend , "netdev@vger.kernel.org" , "David S. Miller" , Neil Horman , Andy Gospodarek , Daniel Borkmann , Or Gerlitz , Jesse Gross , Pravin Shelar , Andy Zhou , Ben Hutchings , Stephen Hemminger , Jeff Kirsher , Vladislav Yasevich , Cong Wang , Eric Dumazet , Scott Feldman , Florian Fainelli , Roopa Prabhu , John To: John Fastabend , Tom Herbert Return-path: Received: from mail-ig0-f180.google.com ([209.85.213.180]:37384 "EHLO mail-ig0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755817AbaIWLJU (ORCPT ); Tue, 23 Sep 2014 07:09:20 -0400 Received: by mail-ig0-f180.google.com with SMTP id a13so4339258igq.1 for ; Tue, 23 Sep 2014 04:09:19 -0700 (PDT) In-Reply-To: <5420CEAC.2070104@gmail.com> Sender: netdev-owner@vger.kernel.org List-ID: 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 >