[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100831004827.GE11594@verge.net.au>
Date: Tue, 31 Aug 2010 09:48:27 +0900
From: Simon Horman <horms@...ge.net.au>
To: Chris Wright <chrisw@...s-sol.org>
Cc: "Rose, Gregory V" <gregory.v.rose@...el.com>,
Ben Pfaff <blp@...ira.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Jesse Gross <jesse@...ira.com>,
Stephen Hemminger <shemminger@...ux-foundation.org>,
Herbert Xu <herbert@...dor.hengli.com.au>,
Arnd Bergmann <arnd@...db.de>,
David Miller <davem@...emloft.net>
Subject: Re: [rfc] Merging the Open vSwitch datapath
On Mon, Aug 30, 2010 at 01:59:07PM -0700, Chris Wright wrote:
> * Rose, Gregory V (gregory.v.rose@...el.com) wrote:
> > >From: Ben Pfaff [mailto:blp@...ira.com]
> > >On Mon, Aug 30, 2010 at 11:26:17AM -0700, Rose, Gregory V wrote:
> > >> I just want to put in a plug for the netlink interface. For NICs with
> > >> EVB we'll need it.
> > >
> > >Off-hand, the main reasons to use Netlink, instead of the existing
> > >character device interface, are that Netlink is easier to extend and
> > >that it should reduce or eliminate the 32-to-64 bit compat layer
> > >currently in the Open vSwitch tree.
>
> That, plus it's a typical way to do network configuration. Esp. with
> bi-directional communication. So the userspace bit both listens to
> netlink messages, like any of the routing daemons or lldpad or similar
> do, and sends netlink messasges to update driver's flow table.
>
> BTW, this kind of discussion was why Herbert felt strongly against
> drivers/staging/. He wanted to be sure the interfaces were well-defined
> first.
Hi Chris,
Is the implication that there is a preference for finalising
the interface (as much as that is possible) before merging?
[ snip ]
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists