From owner-freebsd-current Mon Aug 30 15:11:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id B120015867 for ; Mon, 30 Aug 1999 15:11:13 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id PAA77782; Mon, 30 Aug 1999 15:09:48 -0700 (PDT) Date: Mon, 30 Aug 1999 15:10:31 -0700 (PDT) From: Julian Elischer To: Jonathan Lemon Cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: HEADS UP In-Reply-To: <19990830164043.11777@right.PCS> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 30 Aug 1999, Jonathan Lemon wrote: > On Aug 08, 1999 at 11:36:30PM +0200, Poul-Henning Kamp wrote: > > In message <19990830162125.52517@right.PCS>, Jonathan Lemon writes: > > > 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) > > > > Please, can we have them be in milliseconds ? > Wouldn't this mean writing a sysctl proc for each variable, > instead of directly changing the underlying integer? I did > consider this, but wasn't sure if it would be worth the effort. and? you already indicated that setting the value to 0 might be bad. having a generic Usec to Tics handler might be usable if it can also protect against 0 values.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message