On Tue, Jun 29, 2021 at 12:23:21AM +, Rick Macklem wrote:
> I don't understand how multiple TCP connections to the same
> server IP address will distribute the load across multiple network
> interfaces?
Sounds like a bandwith-latency-product issue. TCP is prone to stalling at
the end of a buff
On Tue, 29 Jun 2021 00:23:21 +
Rick Macklem wrote:
> I don't understand how multiple TCP connections to the same
> server IP address will distribute the load across multiple network
> interfaces?
> I thought that lagg would have handled this?
I don't think this targets multiple interface s
On Mon, Jun 28, 2021 at 5:23 PM Rick Macklem wrote:
>
> The Linux NFS client now has a mount option "nconnect",
> which specifies that multiple TCP connections be created
> for an NFS mount, where RPCs are done on the connections,
> in a round robin fashion. (Alternating between the two TCP
> conn
On Mon, Jun 28, 2021 at 6:24 PM Rick Macklem wrote:
> The Linux NFS client now has a mount option "nconnect",
> which specifies that multiple TCP connections be created
> for an NFS mount, where RPCs are done on the connections,
> in a round robin fashion. (Alternating between the two TCP
> conne
The Linux NFS client now has a mount option "nconnect",
which specifies that multiple TCP connections be created
for an NFS mount, where RPCs are done on the connections,
in a round robin fashion. (Alternating between the two TCP
connections for the case of nconnect=2.)
The Linux man page says:
nc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256819
Marek Zarychta changed:
What|Removed |Added
CC||zarych...@plan-b.pwste.edu.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254514
Jeffrey Gelens changed:
What|Removed |Added
CC||jeff...@gelens.org
--- Comment #3
