|
Yep - but it's usually more bandwidth, not more "speed," it's more lanes on the carriageway, not double the speed limit, double the traffic volume not double the velocity.
Basically it's Link Aggregation (IIRC you are familiar with that,) in the end points. I've used it on enterprise class servers in the past, mostly for resilience, but I'll take the extra bandwidth as well. However, in a SOHO LAN with very few stations and users, it might not have such a good use case.
"Out of Order Packet Delivery" (OOPD to it's mates) is a Nemesis in designing network infrastructure, so things such as NIC teaming and Link Aggregation usually try to "design out" OOPD (indeed, standards based LA requires no change in the order of packets of a stream across the channel.)
In olden days before LA got codified into IEEE standards, HP's server "NIC Teaming Driver" used to let you play a few tunes as to how to distribute the load across the channel (such as MAC address hashes, IP address hashes, round robin,) but in the (admittedly few) versions of the standards based teaming/LA I've seen in switches and servers, there was little or no control. |
|