netdev
[Top] [All Lists]

Re: Implementing 802.3ad-2000 link aggregation under Linux

To: Donald Becker <becker@xxxxxxxxx>
Subject: Re: Implementing 802.3ad-2000 link aggregation under Linux
From: Andi Kleen <ak@xxxxxx>
Date: Fri, 25 Aug 2000 13:36:57 +0200
Cc: Ben Greear <greearb@xxxxxxxxxxxxxxx>, Andi Kleen <ak@xxxxxx>, Nick Towers <ncet@xxxxxxxxxxxx>, netdev@xxxxxxxxxxx
In-reply-to: <Pine.LNX.4.10.10008250014300.2339-100000@xxxxxxxxxxxxx>; from becker@xxxxxxxxx on Fri, Aug 25, 2000 at 06:15:37AM +0200
References: <39A5E0D1.A1994489@xxxxxxxxxxxxxxx> <Pine.LNX.4.10.10008250014300.2339-100000@xxxxxxxxxxxxx>
Sender: owner-netdev@xxxxxxxxxxx
On Fri, Aug 25, 2000 at 06:15:37AM +0200, Donald Becker wrote:
> On Thu, 24 Aug 2000, Ben Greear wrote:
> 
> > Subject: Re: Implementing 802.3ad-2000 link aggregation under Linux
> > Andi Kleen wrote:
> > > On Thu, Aug 24, 2000 at 07:43:29PM +0200, Nick Towers wrote:
> > > > 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
> > > 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....
> 
> 802.3ad is not just channel bonding (the kernel-level mechanism), it also
> including sending packets down each link to detect topology and verify that
> the connection continues to work.

The kernel already has all necessary mechanisms for that in place: queryable
neighbour states, after going into slow path the protocol does its own 
checking anyways.

I believe you'll be able to do a fine 802.3ad implementation without 
any kernel changes.

-Andi

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

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