Date: Thu, 08 Feb 2024 12:26:52 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 258732] [tcp] TCP_MAXSEG does not work Message-ID: <bug-258732-7501-l4TIBqfdLV@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-258732-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-258732-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D258732 Arthur Kiyanovski <akiyano@amazon.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |akiyano@amazon.com --- Comment #12 from Arthur Kiyanovski <akiyano@amazon.com> --- (In reply to Michael Tuexen from comment #5) Just adding a usage example: A popular way to sanity test network performance is the iperf tool. With this tool, the way to control the size of packets sent is with the -M parameter, which according to the documentation: -M, --mss n set TCP maximum segment size using TCP_MAXSEG For example, to get a quick look at pps, what one may like to do is to set = the -M parameter to some small number and run the BW test. This gives a good fe= el for pps. There may be other ways to achieve this, but this is the popular quick and dirty one I know. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-258732-7501-l4TIBqfdLV>