From: Ben Pfaff <blp@nicira.com>
To: "Rose, Gregory V" <gregory.v.rose@intel.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Jesse Gross <jesse@nicira.com>,
Stephen Hemminger <shemminger@linux-foundation.org>,
Chris Wright <chrisw@sous-sol.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Arnd Bergmann <arnd@arndb.de>, David Miller <davem@davemloft.net>
Subject: Re: [rfc] Merging the Open vSwitch datapath
Date: Mon, 30 Aug 2010 11:33:28 -0700 [thread overview]
Message-ID: <20100830183328.GI7629@nicira.com> (raw)
In-Reply-To: <43F901BD926A4E43B106BF17856F0755F63A08EE@orsmsx508.amr.corp.intel.com>
[restoring CCs that I inadvertently busted upthread]
On Mon, Aug 30, 2010 at 11:26:17AM -0700, Rose, Gregory V wrote:
> >From: netdev-owner@vger.kernel.org [mailto:netdev-owner@vger.kernel.org]
> >On Behalf Of Ben Pfaff
> >
> >Simon Horman <horms@verge.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?
next prev parent reply other threads:[~2010-08-30 19:06 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-30 6:27 [rfc] Merging the Open vSwitch datapath Simon Horman
2010-08-30 6:52 ` Joe Perches
2010-08-30 7:11 ` Simon Horman
2010-08-30 7:25 ` Joe Perches
2010-08-30 7:33 ` Simon Horman
2010-08-30 17:22 ` Ben Pfaff
2010-08-30 18:26 ` Rose, Gregory V
2010-08-30 18:33 ` Ben Pfaff [this message]
2010-08-30 18:45 ` Rose, Gregory V
2010-08-30 20:59 ` Chris Wright
2010-08-31 0:48 ` Simon Horman
2010-08-31 0:54 ` Chris Wright
2010-08-31 1:01 ` Simon Horman
2010-08-31 1:11 ` Jesse Gross
2010-08-31 1:38 ` Simon Horman
2010-08-31 8:18 ` Herbert Xu
2010-08-30 21:04 ` Arnd Bergmann
2010-08-30 22:15 ` Rose, Gregory V
2010-08-31 11:48 ` Arnd Bergmann
2010-08-31 17:04 ` Rose, Gregory V
2010-08-31 17:43 ` Arnd Bergmann
2010-08-31 20:16 ` Rose, Gregory V
2010-10-15 11:31 ` openvswitch/flow WAS ( " jamal
2010-10-15 16:18 ` Ben Pfaff
2010-10-15 21:35 ` Jesse Gross
2010-10-16 11:35 ` jamal
2010-10-16 19:33 ` Jesse Gross
2010-10-18 12:16 ` jamal
2010-10-18 15:20 ` Simon Horman
2010-10-19 10:22 ` jamal
2010-10-19 14:56 ` Simon Horman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100830183328.GI7629@nicira.com \
--to=blp@nicira.com \
--cc=arnd@arndb.de \
--cc=chrisw@sous-sol.org \
--cc=davem@davemloft.net \
--cc=gregory.v.rose@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=jesse@nicira.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.