Date: Tue, 7 Aug 2001 10:47:34 -0600 From: "Kenneth D. Merry" <ken@kdm.org> To: stanislav shalunov <shalunov@internet2.edu> Cc: net@FreeBSD.ORG Subject: Re: TCP problems with large window sizes on FreeBSD (GigaTCP) Message-ID: <20010807104734.A46031@panzer.kdm.org> In-Reply-To: <87n15inp9r.fsf@cain.internet2.edu>; from shalunov@internet2.edu on Thu, Aug 02, 2001 at 05:08:32PM -0400 References: <200108020503.f7253jY08157@prism.flugsvamp.com> <87y9p2qxvc.fsf@cain.internet2.edu> <87n15inp9r.fsf@cain.internet2.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Aug 02, 2001 at 17:08:32 -0400, stanislav shalunov wrote: > stanislav shalunov <shalunov@internet2.edu> writes: > > > I'll try increasing the value of TI_JSLOTS to 8192 (twice the number > > of 4K packets in 16MB window) and see if it makes a difference. > > FWIW, this seems to have improved the situation and the burst loss > doesn't happen anymore. For those who might care to look at the new > numbers, see http://www.internet2.edu/~shalunov/gigatcp/ > > There seems to be a problem with the ti driver in that it doesn't > recover from the situation of jumbo slots shortage right away after > supply of packets is removed, as one would expect it to. The > condition lingers for a long time afterwards. It seems to recover > eventually, but after quite different time for diffirent conditions: > sometimes it's seconds, sometimes it's minutes. The "slow" case > appears to be an example of fast periodic recovery, while in the > "stalled" case the recovery doesn't happen until the TCP connection > times out. The zero copy version of the ti(4) driver has a different jumbo buffer allocator that may reduce the intstance of problems. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010807104734.A46031>