Date: Mon, 30 Aug 1999 17:31:20 -0500 From: Jonathan Lemon <jlemon@americantv.com> To: Julian Elischer <julian@whistle.com> Cc: "Rodney W. Grimes" <freebsd@gndrsh.dnsmgr.net>, current@FreeBSD.ORG Subject: Re: HEADS UP Message-ID: <19990830173120.30486@right.PCS> In-Reply-To: <Pine.BSF.3.95.990830144937.339I-100000@current1.whistle.com>; from Julian Elischer on Aug 08, 1999 at 03:01:32PM -0700 References: <199908302127.OAA67008@gndrsh.dnsmgr.net> <Pine.BSF.3.95.990830144937.339I-100000@current1.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Aug 08, 1999 at 03:01:32PM -0700, Julian Elischer wrote: > > > On Mon, 30 Aug 1999, Rodney W. Grimes wrote: > > > > I've just committed the revised TCP timer code. There are some > > > user visible changes: > > > > > > User visible TCP timers are now in units of the system clock > > > (10ms for the i386), not those of the slowtimeout (500ms). So > > > if you have customized one of these values, (e.g.: net.inet.tcp.keepintvl), > > > you'll need to multiply it appropriately to keep the same interval. > > I don't want to sound ungrateful, but couldn't we have defined these in > terms of Usecs and translated? > I mean I sometimes compile hz to be 1000 for some reasons.. > this means that I have to reset all these values in my rc scripts. > > As an example the kern.quantum variable that will always be the same > despite a redefinition of Hz. It's stored internally in terms of Hz but > exported in uSecs. Okay, I'll work on this, and should have a patch by tomorrow (unless somone beats to me it). I think that having it in units of usec is probably better than msec; it provides more in the way of "forward compatability", and allows for a larger HZ. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990830173120.30486>