[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160427100745.29976fbc@samsung9>
Date: Wed, 27 Apr 2016 10:07:45 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: David Miller <davem@...emloft.net>
Cc: jiri@...nulli.us, fw@...len.de, nicolas.dichtel@...nd.com,
netdev@...r.kernel.org
Subject: Re: [PATCH net-next] drivers/net: add 6WIND SHULTI support
On Wed, 27 Apr 2016 12:55:06 -0400 (EDT)
David Miller <davem@...emloft.net> wrote:
> From: Jiri Pirko <jiri@...nulli.us>
> Date: Wed, 27 Apr 2016 17:14:04 +0200
>
> > Wed, Apr 27, 2016 at 11:56:15AM CEST, fw@...len.de wrote:
> >>Nicolas Dichtel <nicolas.dichtel@...nd.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.
Also it has a bunch of device specific generic netlink which was
a red flag for me.
Powered by blists - more mailing lists