Date: Sun, 02 Dec 2007 17:43:54 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: "M. Warner Losh" <imp@bsdimp.com> Cc: arch@FreeBSD.org Subject: Re: New "timeout" api, to replace callout Message-ID: <45308.1196617434@critter.freebsd.dk> In-Reply-To: Your message of "Sun, 02 Dec 2007 09:36:03 MST." <20071202.093603.228972203.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20071202.093603.228972203.imp@bsdimp.com>, "M. Warner Losh" writes: >In message: <19827.1196612123@critter.freebsd.dk> > "Poul-Henning Kamp" <phk@phk.freebsd.dk> writes: >: In message <20071202.085545.177225588.imp@bsdimp.com>, "M. Warner Losh" writes: >: >: >There are a number of places in the tree that use a parameter of '1' >: >today to mean "next time that's convenient." Some of these places are >: >clever and know that HZ is never < 100 or > 1000 (or so they think), >: >while others are just sloppy code. >: >: Yes, but those can hardly be called "concrete" in terms of wanting >: to know what they mean, can they ? :-) >: >: The only way I can see we can deal with them in the short term, >: is to ask for timeouts of "1000000 / hz, TIMEOUT_USEC" > >Or have a "timeout_soon" function like you have the other timeout >conversion routines. I'm not very keen on offering too much rope. Intelligent decisions need to be made about these polling rates and making it too easy to not think about it would be to encourage bad practices. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45308.1196617434>