On 8/25/15 3:47 PM, Chris Stankevitz wrote:
Can anyone explain my abysmally small TCP window?
So I believe this is the story:
1. openssh limits the size of some outgoing buffer to 65KB
2. openssh/HPN tries to improve on this by increasing the size of the
outgoing buffer to match getsockopt(SO_SNDBUF)
3. When asked for the current SO_SNDBUF, FreeBSD 10.1 reports the high
watermark of the outgoing buffer, not its capacity.
4. (2) is essentially a no-op because of (3).
5. openssh/HPN can be tricked into increasing its outgoing buffer by
increasing sendspace/recvspace
My comments:
- (3) is not what I would expect -- perhaps the ssh/HPN folks would
agree with me. Shouldn't getsockopt(SO_SNDBUF) return the same value
set by setsockopt(SO_SNDBUF)?
- I do not understand the mechanism by which (5) works.
Chris
_______________________________________________
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
