Why ALB? Assuming that outgoing throughput is a concern, balance-rr is better. The upside to stuff like ALB and other L3+L4 or L2 hashing methods is to avoid packet reordering issues. But I did the math a few years back, and iirc at 10Gbit there has to be a difference of ~50ft to reorder a stream of 64byte packets. Checking with WolframAlpha: 64bytes/(10Gbit/sec) = ~51nsec or ~50ft. For most purposes and something running on a standard CPU, balance-rr is simpler. This doesn't apply to ASICs and other network silicon though... Sent from myPhone.
On Sep 9, 2024, at 7:25 AM, Roger Oberholtzer <roger.oberholtzer@gmail.com> wrote:
On Mon, Sep 9, 2024 at 11:58 AM Andrei Borzenkov <arvidjaar@gmail.com> wrote:
On Mon, Sep 9, 2024 at 12:39 PM Roger Oberholtzer <roger.oberholtzer@gmail.com> wrote:
The situation is that the Windows computer can access the Linux computer via this network (via ssh). The Linux system, otoh, cannot access the Windows computer.
What does "access the Windows" mean? How exactly are you accessing.
ping as start. And ssh, as it will be rsync via sh that this network will primarily be doing.
Windows? Are bond modes the same on Windows and Linux?
That's always the fun part. Windows and Linux use different names for these things.
What I am after is maximizing throughput. On Linux, it seems like balance-alb is what I would like. So what is the compatible Windows NIC Team setting to match this? I've not figured that out yet.
-- Roger Oberholtzer