From owner-freebsd-net  Fri Feb  9 14:46:16 2001
Delivered-To: freebsd-net@freebsd.org
Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10])
	by hub.freebsd.org (Postfix) with ESMTP
	id 9514137B67D; Fri,  9 Feb 2001 14:45:51 -0800 (PST)
Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1])
	by whizzo.transsys.com (8.11.1/8.11.0) with ESMTP id f19MhFC11639;
	Fri, 9 Feb 2001 17:43:16 -0500 (EST)
	(envelope-from louie@whizzo.transsys.com)
Message-Id: <200102092243.f19MhFC11639@whizzo.transsys.com>
X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4
To: Alex Pilosov <alex@pilosoft.com>
Cc: Chris Dillon <cdillon@wolves.k12.mo.us>,
	Dan Nelson <dnelson@emsphone.com>, Bill Paul <wpaul@FreeBSD.ORG>,
	hackers@FreeBSD.ORG, net@FreeBSD.ORG
X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg
From: "Louis A. Mamakos" <louie@TransSys.COM>
Subject: Re: call for testers: port aggregation netgraph module 
References: <Pine.BSO.4.10.10102091721400.31680-100000@spider.pilosoft.com> 
In-reply-to: Your message of "Fri, 09 Feb 2001 17:23:02 EST."
             <Pine.BSO.4.10.10102091721400.31680-100000@spider.pilosoft.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 09 Feb 2001 17:43:15 -0500
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


The crock in these trunking schemes is all the trouble and effort expended
to avoid re-ordering frames across the trunk bundle.  This is why you
see things like the hashing techniques so that an individual flow of
traffic doesn't get reordered because it always is serialized over the
a single path.

I'll observe that there's nothing in the IP architecture which (should)
rely on packets not being reordered.  I'll also observe that in a network
with multiple ethernet switching running a spanning-tree protocol, you
probably should't rely on packet reordering never happening when
a link fails and the spanning tree computation is re-run.

So, a clever implementation might choose to drain a single queue rather
than having multiple queues, one per network interface. 

Of course, some network stacks don't deal well with TCP segments arriving
out-of-order, but they are just broken.

louie



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message