| To: | "David S. Miller" <davem@xxxxxxxxxx> |
|---|---|
| Subject: | Re: bonding vs 802.3ad/Cisco EtherChannel link agregation |
| From: | Chris Friesen <cfriesen@xxxxxxxxxxxxxxxxxx> |
| Date: | Mon, 16 Sep 2002 17:22:30 -0400 |
| Cc: | greearb@xxxxxxxxxxxxxxx, cacophonix@xxxxxxxxx, linux-net@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| References: | <3D860246.3060609@candelatech.com> <20020916.125555.36549381.davem@redhat.com> <3D8648AE.DD498ECE@nortelnetworks.com> <20020916.140453.72638827.davem@redhat.com> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
"David S. Miller" wrote: > From: Chris Friesen <cfriesen@xxxxxxxxxxxxxxxxxx> > > Okay, that makes me even more curious why we don't send successive > packets out successive pipes in a bonded link. > > This is not done because it leads to packet reordering which > if bad enough can trigger retransmits. > > Scott Feldman's posting mentioned this, as did one other I > think. I did see those posts, but then I saw yours on how the linux receive end does the right thing with regards to reordering, and that confused me. So if I have it right linux-linux could theoretically work okay with a single stream over multiple links (potentially causing lots of reordering), but linux-router would not work well. Chris |
| Previous by Date: | Re: bonding vs 802.3ad/Cisco EtherChannel link agregation, David S. Miller |
|---|---|
| Next by Date: | Re: bonding vs 802.3ad/Cisco EtherChannel link agregation, David S. Miller |
| Previous by Thread: | Re: bonding vs 802.3ad/Cisco EtherChannel link agregation, David S. Miller |
| Next by Thread: | Re: bonding vs 802.3ad/Cisco EtherChannel link agregation, David S. Miller |
| Indexes: | [Date] [Thread] [Top] [All Lists] |