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: <CAEP_g=8uJnngfKJRGLLnd8U7M9aJTfOSUheB62-O7OX6Ud0DLw@mail.gmail.com>
Date:	Sat, 1 Oct 2011 11:15:01 -0700
From:	Jesse Gross <jesse@...ira.com>
To:	Jiri Pirko <jpirko@...hat.com>
Cc:	netdev@...r.kernel.org, davem@...emloft.net,
	eric.dumazet@...il.com, bhutchings@...arflare.com,
	shemminger@...tta.com, fubar@...ibm.com, andy@...yhouse.net,
	tgraf@...radead.org, ebiederm@...ssion.com, mirqus@...il.com,
	kaber@...sh.net, greearb@...delatech.com
Subject: Re: [RFC patch net-next-2.6] net: introduce ethernet teaming device

On Fri, Sep 30, 2011 at 5:44 AM, Jiri Pirko <jpirko@...hat.com> wrote:
> This patch introduces new network device called team. It supposes to be
> very fast, simple, userspace-driven parallel to existing bonding device.
> Userspace library called libteam with couple of demo apps is available
> here:
> https://github.com/jpirko/libteam
> Note it's still in its dipers atm.
>
> team<->libteam use generic netlink for communication. That and rtnl
> suppose to be the only way to configure team device, no sysfs etc.
>
> In near future python binding for libteam will be introduced. Also
> daemon providing arpmon/miimon active-backup functionality will
> be introduced. All what's necessary is already implemented in kernel team
> driver.
>
> Plan is to support 8023ad in near future with it's logic mainly in
> userspace daemon as well.
>
> Please review, try, comment. All feedback would be much appreciated.
>
> Signed-off-by: Jiri Pirko <jpirko@...hat.com>

Not to push my own agenda too much but you might want to take a look
at Open vSwitch.  It uses the same strategy of userspace directed
bonding and already supports active-backup, 802.3ad, and quite a few
other networking tools all controlled by userspace.

I know there's been a lot of talk and not a lot of action when it
comes to upstreaming but that's changing.  We're fixing up a few loose
ends in the userspace/kernel interface and then intend to propose a
patch fairly soon.
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ