Date: Tue, 10 Nov 2015 21:41:47 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 204438] setsockopt() handling of kern.ipc.maxsockbuf limit Message-ID: <bug-204438-8-c2jRpOJNSD@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-204438-8@https.bugs.freebsd.org/bugzilla/> References: <bug-204438-8@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=204438 Allan Jude <allanjude@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |allanjude@FreeBSD.org --- Comment #1 from Allan Jude <allanjude@FreeBSD.org> --- I have run into this, but never understood why it happened, just worked around it. in openssh-portable with HPN enabled, I tried to use '-oTcpRcvBuf=4M' to increase the socket buffer size to receive large ZFS replication streams more quickly. Of course, with kern.ipc.maxsockbuf set to 4M, this fails, I have to use 3.5M or something. This patch would seem to solve that. Thank you. The biggest question is, why can't I actually use a sockbuf for 4M? -- 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-204438-8-c2jRpOJNSD>