Date: Fri, 08 Oct 2021 09:03:44 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 258732] [tcp] TCP_MAXSEG does not work Message-ID: <bug-258732-7501-H6ALlJfIKW@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=258732 --- Comment #9 from Michael Tuexen <tuexen@freebsd.org> --- (In reply to zhh0000zhh from comment #8) Sure, the MSS can be different in each direction. Each node declares its maximum receive size. However, I do not understand * How the Nagle algorithm is involved in this discussion * Why an application cares about the MSS. TCP is a byte stream. At the API level you have no guarantee that the data you receive has any relation to the segmentation which was used by the peer. On the sending side, you don't have to care about the segmentation process. -- 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-H6ALlJfIKW>