Date: Fri, 14 Oct 2005 12:52:24 -0500 From: Eric Anderson <anderson@centtech.com> To: fs@freebsd.org Subject: Re: FreeBSD NFS server not responding to TCP SYN packets from Linux/SunOS clients Message-ID: <434FF058.1010800@centtech.com> In-Reply-To: <200510141750.NAA24051@snowhite.cis.uoguelph.ca> References: <200510141750.NAA24051@snowhite.cis.uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
rick@snowhite.cis.uoguelph.ca wrote: > [good stuff snipped] > >>threads), but they wait until the disks are not busy. I'm not really >>sure what it would give you to have the nfsd's wait until disk is not as >>busy, as that is what it is doing now, right? Maybe you would smooth > > > The difference is that, if the nfsd threads don't take the request off > the socket receive queue, then the TCP send window slows/stops new > requests being sent from the client at some point. > > Currently, the nfsd thread takes the request off the TCP sockets receive > queue and then sleeps inside the VFS/VnodeOp calls. > (As noted in the previous email, I think what happens now is good enough > for most cases, so long as the client doesn't retry the RPCs. I had > forgotten that the TCP seq# would cause TCP level retransmits to be > discarded, even after the request is removed from the receive queue.) Then what happens when the socket receive queue fills up? (Sorry if this is obvious). Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?434FF058.1010800>