Date: Thu, 04 Aug 2005 09:16:31 +1000 From: Dave+Seddon <dave-sender-1932b5@seddon.ca> To: freebsd-net@freebsd.org Subject: Re: running out of mbufs? Message-ID: <1123110992.91393.TMDA@seddon.ca> In-Reply-To: <42F082A2.1050908@thedarkside.nl> References: <1123040973.95445.TMDA@seddon.ca> <20050802225518.G53516@odysseus.silby.com> <42F082A2.1050908@thedarkside.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
Perhaps a quick "fix" to the bug would be to output a message to the console when somebody tried to set the tcp.sendspace or tcp.recvspace space > 65535 * 2. Regards, Dave Seddon Pieter de Boer writes: > Mike Silbersack wrote: > >>> net.inet.tcp.sendspace=1024000 >>> net.inet.tcp.recvspace=1024000 >>> kern.ipc.maxsockbuf=20480000 >> I don't think large socket buffers have been tested well, it's possible >> that you're exhausting almost all of your mbufs with just a few >> connections - if you're really stuffing that much data in. I'd go back >> to the default settings for the above and try again. > > With the added note that the send/recv spaces should be 65535 * 2^x (which > 1024000 isn't). I might add that there's still a bug in the calculation of > the TCP window scale option with regards to the set window size, leading > to a FreeBSD system advertising a too large recvspace, which makes setting > this option right even more necessary. > (http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/82470) > > -- > Pieter > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1123110992.91393.TMDA>