netdev
[Top] [All Lists]

Re: Implementing 802.3ad-2000 link aggregation under Linux

To: Ben Greear <greearb@xxxxxxxxxxxxxxx>
Subject: Re: Implementing 802.3ad-2000 link aggregation under Linux
From: Andi Kleen <ak@xxxxxx>
Date: Fri, 25 Aug 2000 13:34:45 +0200
Cc: Andi Kleen <ak@xxxxxx>, Nick Towers <ncet@xxxxxxxxxxxx>, netdev@xxxxxxxxxxx
In-reply-to: <39A5E0D1.A1994489@xxxxxxxxxxxxxxx>; from greearb@xxxxxxxxxxxxxxx on Fri, Aug 25, 2000 at 04:11:53AM +0200
References: <39A55DEB.94242945@xxxxxxxxxxxx> <20000824202203.A4710@xxxxxxxxxxx> <39A5E0D1.A1994489@xxxxxxxxxxxxxxx>
Sender: owner-netdev@xxxxxxxxxxx
On Fri, Aug 25, 2000 at 04:11:53AM +0200, Ben Greear wrote:
> Andi Kleen wrote:
> > 
> > On Thu, Aug 24, 2000 at 07:43:29PM +0200, Nick Towers wrote:
> > > Hello,
> > >
> > > I am looking at starting a project to implment 802.3ad ethernet link
> > > aggregation under Linux. For those of you that have never heard of it
> > > I've given a description and a few pointers at the end. Before I
> > > launch into it I was wondering if there is anyone else out there who
> > >
> > > 1) Has started work on an implementation
> > 
> > I started work some time ago. It is basically an user space problem.
> 
> How would it be user-space?  Doesn't it aggregate several physical
> layers together into one interface?  That seems like a kernel
> level thing to me....

The required kernel level mechanisms already exit: bounding, teql,
equal cost multipath routing. Only multipath routing is strictly
conforming to the SPEC of keeping an "conversation" on the same line.

Anyways, you just need a routing daemon in user space that listens
to the multicast group and sets up the required bundles via one of these
mechanisms.


-Andi

-- 
This is like TV. I don't like TV.

<Prev in Thread] Current Thread [Next in Thread>