All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <chris.friesen@genband.com>
To: Phillip Susi <psusi@cfl.rr.com>
Cc: David Lamparter <equinox@diac24.net>, netdev@vger.kernel.org
Subject: Re: 802.3ad bonding brain damaged?
Date: Mon, 08 Aug 2011 14:14:35 -0600	[thread overview]
Message-ID: <4E4043AB.1060500@genband.com> (raw)
In-Reply-To: <4E4041B5.5040908@cfl.rr.com>

On 08/08/2011 02:06 PM, Phillip Susi wrote:
> On 8/8/2011 3:57 AM, David Lamparter wrote:
>> No, it isn't. 802.3ad/.1AX explicitly requires that no packet
>> re-ordering may ever occur, which can only be guaranteed by enqueueing
>> packets for one host on one TX interface. This behaviour is mandated by
>> 802.1AX-2008 page 15 which reads:
>
> Outch, that does cause a big problem for store-and-forward switching.
> You basically can't split up packets from a single stream without very
> careful cut-through switching, which we obviously can't do in Linux.
> That seems a rather silly requirement given that higher level protocols
> already deal with packet reordering. Why not an option to say stuff the
> standard?

Bonding doesn't know about "higher level protocols".  Also, assuming 
that higher level protocols already deal with reordering can be 
dangerous.  I've dealt with network protocols and apps that assumed 
there would be no reordering because at the time they were written they 
used point-to-point links.  They actually work fairly well with single 
links, so it would be reasonable to try and keep them working with 
bonded links.

Chris

-- 
Chris Friesen
Software Developer
GENBAND
chris.friesen@genband.com
www.genband.com

  parent reply	other threads:[~2011-08-08 20:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-07 19:52 802.3ad bonding brain damaged? Phillip Susi
2011-08-08  7:57 ` David Lamparter
2011-08-08 15:59   ` Eric Dumazet
2011-08-08 16:44     ` Jay Vosburgh
2011-08-08 20:06   ` Phillip Susi
2011-08-08 20:08     ` Chris Adams
2011-08-08 20:14     ` Chris Friesen [this message]
2011-08-08 20:32       ` Phillip Susi
2011-08-08 20:42         ` Ben Hutchings
2011-08-09 11:24         ` Benny Amorsen
2011-08-08 20:54     ` Rick Jones

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E4043AB.1060500@genband.com \
    --to=chris.friesen@genband.com \
    --cc=equinox@diac24.net \
    --cc=netdev@vger.kernel.org \
    --cc=psusi@cfl.rr.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.