Gerrit Kuehn wrote:
>On Fri, 27 Aug 2021 14:55:52 +
>Rick Macklem wrote:
>
>> >https://reviews.freebsd.org/R10:1e0a518d65488caafff89a4ecba9cfb2be233379
>> >
>> >I guess I'm still too unfamiliar with the new code repository. How
>> >would I find out now where this ended up, i.e., in which branc
On Fri, 27 Aug 2021 14:55:52 +
Rick Macklem wrote:
> >https://reviews.freebsd.org/R10:1e0a518d65488caafff89a4ecba9cfb2be233379
> >
> >I guess I'm still too unfamiliar with the new code repository. How
> >would I find out now where this ended up, i.e., in which branches
> >(HEAD, 13-stable,
Gerrit Kuehn wrote:
>Rick Macklem wrote:
>
>> >In case anyone is interested in testing and/or reviewing the patch,
>> >it is at https://reviews.freebsd.org/D30970.
>
>> The phabricator patch has been updated. Please test/review/comment.
>
>Sorry for picking this old thread up again, but I have a q
On Fri, 2 Jul 2021 02:40:49 +
Rick Macklem wrote:
> >In case anyone is interested in testing and/or reviewing the patch,
> >it is at https://reviews.freebsd.org/D30970.
> The phabricator patch has been updated. Please test/review/comment.
Sorry for picking this old thread up again, but I
on
Sent: Tuesday, June 29, 2021 5:11 AM
To: Rick Macklem
Cc: freebsd-net
Subject: Re: RFC: NFS trunking (multiple TCP connections for a mount
CAUTION: This email originated from outside of the University of Guelph. Do not
click links or open attachments unless you recognize the sender and know the
co
for your input, rick
From: Peter Eriksson
Sent: Tuesday, June 29, 2021 5:11 AM
To: Rick Macklem
Cc: freebsd-net
Subject: Re: RFC: NFS trunking (multiple TCP connections for a mount
CAUTION: This email originated from outside of the University of Guelph. D
n is worth implementing.
Thanks for your input, rick
From: Peter Eriksson
Sent: Tuesday, June 29, 2021 5:11 AM
To: Rick Macklem
Cc: freebsd-net
Subject: Re: RFC: NFS trunking (multiple TCP connections for a mount
CAUTION: This email originated from outs
> 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?
A lagg typically keeps all data in a TCP stream on a specific lagg member
(depending on how the lagg i
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
13 matches
Mail list logo
