diff options
author | obrien <obrien@FreeBSD.org> | 2001-07-13 18:38:04 +0000 |
---|---|---|
committer | obrien <obrien@FreeBSD.org> | 2001-07-13 18:38:04 +0000 |
commit | c5393097b30c559d7e1cf2d3bf55f22979223051 (patch) | |
tree | 13537095e2a80772447ad2a155df5e7ad7ea660b | |
parent | 15292fece4d326d62a9f19f36b5ca28d42ce54f3 (diff) | |
download | FreeBSD-src-c5393097b30c559d7e1cf2d3bf55f22979223051.zip FreeBSD-src-c5393097b30c559d7e1cf2d3bf55f22979223051.tar.gz |
Bump net.inet.tcp.sendspace to 32k and net.inet.tcp.recvspace to 65k.
This should help us in nieve benchmark "tests".
It seems a wide number of people think 32k buffers would not cause major
issues, and is in fact in use by many other OS's at this time. The
receive buffers can be bumped higher as buffers are hardly used and several
research papers indicate that receive buffers rarely use much space at all.
Submitted by: Leo Bicknell <bicknell@ufp.org>
<20010713101107.B9559@ussenterprise.ufp.org>
Agreed to in principle by: dillon (at the 32k level)
-rw-r--r-- | sys/netinet/tcp_usrreq.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/sys/netinet/tcp_usrreq.c b/sys/netinet/tcp_usrreq.c index de1aa65..1bb7e64 100644 --- a/sys/netinet/tcp_usrreq.c +++ b/sys/netinet/tcp_usrreq.c @@ -995,10 +995,10 @@ tcp_ctloutput(so, sopt) * sizes, respectively. These are obsolescent (this information should * be set by the route). */ -u_long tcp_sendspace = 1024*16; +u_long tcp_sendspace = 1024*32; SYSCTL_INT(_net_inet_tcp, TCPCTL_SENDSPACE, sendspace, CTLFLAG_RW, &tcp_sendspace , 0, "Maximum outgoing TCP datagram size"); -u_long tcp_recvspace = 1024*16; +u_long tcp_recvspace = 1024*64; SYSCTL_INT(_net_inet_tcp, TCPCTL_RECVSPACE, recvspace, CTLFLAG_RW, &tcp_recvspace , 0, "Maximum incoming TCP datagram size"); |