From: Phillip Susi <psusi@cfl.rr.com>
To: Chris Friesen <chris.friesen@genband.com>
Cc: David Lamparter <equinox@diac24.net>, netdev@vger.kernel.org
Subject: Re: 802.3ad bonding brain damaged?
Date: Mon, 08 Aug 2011 16:32:15 -0400 [thread overview]
Message-ID: <4E4047CF.5030705@cfl.rr.com> (raw)
In-Reply-To: <4E4043AB.1060500@genband.com>
On 8/8/2011 4:14 PM, Chris Friesen wrote:
> 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.
Try, sure, but if you can't without seriously affecting performance,
then having a knob for damn the torpedoes, full speed ahead mode seems
reasonable.
I wonder how it is that people have reported that Windows machines
manage to do this? Come to think of it, can windows even bond in
software? Maybe it's only possible on Windows with dual port cards
where the drivers and hardware can make sure that the bonded interfaces
service a single queue and maintain ordering that way?
next prev parent reply other threads:[~2011-08-08 20:32 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
2011-08-08 20:32 ` Phillip Susi [this message]
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=4E4047CF.5030705@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=chris.friesen@genband.com \
--cc=equinox@diac24.net \
--cc=netdev@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).