From: David Miller <davem@davemloft.net>
To: jiri@resnulli.us
Cc: fw@strlen.de, nicolas.dichtel@6wind.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] drivers/net: add 6WIND SHULTI support
Date: Wed, 27 Apr 2016 12:55:06 -0400 (EDT) [thread overview]
Message-ID: <20160427.125506.1088576804354580011.davem@davemloft.net> (raw)
In-Reply-To: <20160427151336.GB1962@nanopsycho.orion>
From: Jiri Pirko <jiri@resnulli.us>
Date: Wed, 27 Apr 2016 17:14:04 +0200
> Wed, Apr 27, 2016 at 11:56:15AM CEST, fw@strlen.de wrote:
>>Nicolas Dichtel <nicolas.dichtel@6wind.com> wrote:
>>> This patch adds the support of the 6WIND SHULTI switch. It is a software
>>> switch doing L2 forwarding.
>>>
>>> This first version implements the minimum needed to get the device working.
>>> It also implements, via switchdev and rtnetlink, bridge forwarding offload,
>>> including FDB static entries, FDB learning and FDB ageing.
>>
>>How is this different from net/bridge?
>>How is this different from openvswitch?
>
> The difference is that it this tries to allow userspace crap to mirror
> setting user does for bridge/ovs. Basically this looks to me like an
> attempt to enable userspace SDKs and such.
+1
There is no way I'm applying this.
next prev parent reply other threads:[~2016-04-27 16:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 9:37 [PATCH net-next] drivers/net: add 6WIND SHULTI support Nicolas Dichtel
2016-04-27 9:50 ` Jiri Pirko
2016-04-27 9:56 ` Florian Westphal
2016-04-27 15:14 ` Jiri Pirko
2016-04-27 15:38 ` Nicolas Dichtel
2016-04-27 15:54 ` Jiri Pirko
2016-04-27 16:55 ` David Miller [this message]
2016-04-27 17:07 ` Stephen Hemminger
2016-04-28 12:00 ` Nicolas Dichtel
2016-04-28 11:59 ` Nicolas Dichtel
2016-04-28 14:05 ` Or Gerlitz
2016-04-28 15:54 ` David Miller
2016-04-29 8:48 ` Nicolas Dichtel
2016-05-01 15:27 ` Jiri Pirko
2016-05-01 19:53 ` Jiri Pirko
2016-05-01 15:24 ` Jiri Pirko
2016-04-27 16:34 ` David Miller
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=20160427.125506.1088576804354580011.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).