netdev - Re: [rfc] Merging the Open vSwitch datapath

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20100830183328.GI7629@nicira.com>
Date:	Mon, 30 Aug 2010 11:33:28 -0700
From:	Ben Pfaff <blp@...ira.com>
To:	"Rose, Gregory V" <gregory.v.rose@...el.com>
Cc:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	Jesse Gross <jesse@...ira.com>,
	Stephen Hemminger <shemminger@...ux-foundation.org>,
	Chris Wright <chrisw@...s-sol.org>,
	Herbert Xu <herbert@...dor.apana.org.au>,
	Arnd Bergmann <arnd@...db.de>,
	David Miller <davem@...emloft.net>
Subject: Re: [rfc] Merging the Open vSwitch datapath

[restoring CCs that I inadvertently busted upthread]

On Mon, Aug 30, 2010 at 11:26:17AM -0700, Rose, Gregory V wrote:
> >From: netdev-owner@...r.kernel.org [mailto:netdev-owner@...r.kernel.org]
> >On Behalf Of Ben Pfaff
> >
> >Simon Horman <horms@...ge.net.au> writes:
> >
> >>    * Possible use of netlink for user-space interface
> >
> >I'm working on this one this week, for what it's worth.
> 
> 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.

Why will NICs with EVB require Netlink for the Open vSwitch interface?
--
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