Date: Tue, 12 Mar 2024 13:39:03 +0000 From: Nuno Teixeira <eduardo@freebsd.org> To: tuexen@freebsd.org Cc: current@freebsd.org, net@freebsd.org Subject: Re: Request for Testing: TCP RACK Message-ID: <CAFDf7U%2BU3QpgsG-hY0u3tC_X9WKSRzuAM7Nfhzu-%2BqPBbs1nng@mail.gmail.com> In-Reply-To: <42C327BD-6CE4-43AA-A1AE-3BEC08D623DB@freebsd.org> References: <42C327BD-6CE4-43AA-A1AE-3BEC08D623DB@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, I'm curious about tcp RACK. As I do not run on a server background, only a laptop and a rpi4 for poudriere, git, browsing, some torrent and ssh/sftp connections, will I see any difference using RACK? What tests should I do for comparison? Thanks, <tuexen@freebsd.org> escreveu (quinta, 16/11/2023 =C3=A0(s) 15:10): > > Dear all, > > recently the main branch was changed to build the TCP RACK stack > which is a loadable kernel module, by default: > https://cgit.FreeBSD.org/src/commit/?id=3D3a338c534154164504005beb00a3c6f= eb03756cc > > As discussed on the bi-weekly transport call, it would be great if people > could test the RACK stack for their workload. Please report any problems = to the > net@ mailing list or open an issue in the bug tracker and drop me a note = via email. > This includes regressions in CPU usage, regressions in performance or any= other > unexpected change you observe. > > You can load the kernel module using > kldload tcp_rack > > You can make the RACK stack the default stack using > sysctl net.inet.tcp.functions_default=3Drack > > Based on the feedback we get, the default stack might be switched to the > RACK stack. > > Please let me know if you have any questions. > > Best regards > Michael > > > --=20 Nuno Teixeira FreeBSD Committer (ports)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFDf7U%2BU3QpgsG-hY0u3tC_X9WKSRzuAM7Nfhzu-%2BqPBbs1nng>