Re: Chelsio / cxlv(4): strange messages, SR-IOV interface does not work

2024-10-23 Thread Navdeep Parhar
On Tue, Oct 22, 2024 at 11:21 PM Lexi Winter wrote: > hello, > > i'm trying to configure a cxlv(4) device, which is a VF of a Chelsio > T540-CR on a host running bhyve. > > host: FreeBSD 15.0-CURRENT #3 lf/main-n269068-2cff93ced1d: Wed Oct 23 > 02:48:20 BST 2024 > guest: FreeBSD 15.0-CURRENT #2 l

Re: Performance test for CUBIC in stable/14

2024-10-23 Thread void
On Wed, Oct 23, 2024 at 03:14:08PM -0400, Cheng Cui wrote: I see. The result of `newreno` vs. `cubic` shows non-constant/infrequent packet retransmission. So TCP congestion control has little impact on improving the performance. The performance bottleneck may come from somewhere else. For exampl

Re: Performance test for CUBIC in stable/14

2024-10-23 Thread Cheng Cui
I see. The result of `newreno` vs. `cubic` shows non-constant/infrequent packet retransmission. So TCP congestion control has little impact on improving the performance. The performance bottleneck may come from somewhere else. For example, the sender CPU shows 97.7% utilization. Would there be any

Re: Performance test for CUBIC in stable/14

2024-10-23 Thread void
On Wed, Oct 23, 2024 at 08:28:01AM -0400, Cheng Cui wrote: The latency does not sound a problem to me. What is the performance of TCP congestion control algorithm `newreno`? In case you need to load `newreno` first. cc@n1:~ % sudo kldload newreno cc@n1:~ % sudo sysctl net.inet.tcp.cc.algorithm

Re: Performance test for CUBIC in stable/14

2024-10-23 Thread Cheng Cui
The latency does not sound a problem to me. What is the performance of TCP congestion control algorithm `newreno`? In case you need to load `newreno` first. cc@n1:~ % sudo kldload newreno cc@n1:~ % sudo sysctl net.inet.tcp.cc.algorithm=newreno net.inet.tcp.cc.algorithm: cubic -> newreno cc@n1:

Re: panic: tcp_do_segment: sent too much

2024-10-23 Thread Michael Tuexen
> On 23. Oct 2024, at 09:42, Peter Holm wrote: > > On Wed, Oct 23, 2024 at 08:32:05AM +0200, Michael Tuexen wrote: >>> On 23. Oct 2024, at 07:51, Peter Holm wrote: >>> >>> + export 'tcpINCARNATIONS=16678' >>> + [ 16678 -le 0 ] >>> + export 'TESTPROGS= ./testcases/tcp/tcp' >>> + sleep 900 >>> +

Re: TCP Success Story (was Re: TCP_RACK, TCP_BBR, and firewalls)

2024-10-23 Thread void
On Wed, Jul 17, 2024 at 02:00:31PM -0600, Alan Somers wrote: So I benchmarked all available congestion control algorithms for single download streams. The results are summarized in the table below. Sorry for resurrecting an old thread, but I note your testing was with single streams. What ar

Re: panic: tcp_do_segment: sent too much

2024-10-23 Thread Peter Holm
On Wed, Oct 23, 2024 at 08:32:05AM +0200, Michael Tuexen wrote: > > On 23. Oct 2024, at 07:51, Peter Holm wrote: > > > > + export 'tcpINCARNATIONS=16678' > > + [ 16678 -le 0 ] > > + export 'TESTPROGS= ./testcases/tcp/tcp' > > + sleep 900 > > + su test -c '(cd ..; ./testcases/run/run $TESTPROGS)'