Date: Fri, 21 Nov 2008 23:19:57 -0500 From: "Jason Fines" <jason.fines@gmail.com> To: freebsd-virtualization@freebsd.org Subject: Question About TCP Reassembly Inside VImages Message-ID: <5e6025b70811212019h64feb7dcrd02ab78ba1b558c3@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
Hello all, I've got a question about setting the sysctl variable net.inet.tcp.reass.maxsegments to a non-zero value inside my vimages. I'm currently running the FreeBSD 7 with the VIMAGE package available at http://imunes.tel.fer.hr/virtnet/vimage_7-20081015.tgz. My problem is with TCP reassembly support inside of the vimages, namely with the tcp.reass.maxsegments sysctl variable. I've tracked down where in the code the variable is set to line 122 in tcp_reass_init() of netinet/tcp_reass.c: "V_tcp_reass_maxseg = nmbclusters / 16;". The line clearly reads that maxsegments should be set to "nmbclusters /16", in the main OS (not in any vimage) the value is correctly set to 1/16 of what my nmbclusters sysctl variable is set to. However, inside all my vimages nmbclusters is set correctly, while reass.maxsegments is incorrectly set to zero!!! Is it possible that nmbclusters when read on line 122 of netinet/tcp_reass.c is zero? Has anyone else experienced this problem? Is TCP reassembly not supported/tested inside vimages? Any help in this area would be greatly appreciated. Thanks, Jason P.S. This technology is phenomenal, and thanks to everyone who is involved developing it.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5e6025b70811212019h64feb7dcrd02ab78ba1b558c3>