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 [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
