Date: Sun, 9 Mar 2008 04:17:22 -0500 (CDT) From: Mike Silbersack <silby@silby.com> To: Jake Rizzo <rizzojake@gmail.com> Cc: freebsd-net@freebsd.org Subject: Re: RELENG-7 tcp connectivity problems with certain clients Message-ID: <20080309041601.X37603@odysseus.silby.com> In-Reply-To: <b07c271a0803090109u1da6b657rcc0bfc63f93c9754@mail.gmail.com> References: <b07c271a0803071455q4c44b626hf93ccad27ffed5ec@mail.gmail.com> <20080307185203.J27119@niwun.pair.com> <b07c271a0803090109u1da6b657rcc0bfc63f93c9754@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 9 Mar 2008, Jake Rizzo wrote: > The patch didn't work, but doing this: > > sysctl net.inet.tcp.tso=0 > sysctl net.inet.tcp.sack.enable=0 > > Allows the client to connect again. Since my ifconfig doesn't show that my > nic supports TSO then I presume it's the sack sysctl that's making it work. > > The machine's a webserver serving almost exclusively dynamic content - with > sack disabled is it likely to affect performance much? > > Thanks, > Jake SACK makes retransmission more effective in some circumstances when packet loss occurs. So, you're probably not going to notice it being disabled at all. In fact. FreeBSD 4.x didn't have any SACK support whatsoever. -Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080309041601.X37603>