Date: Sun, 02 Dec 2007 09:36:03 -0700 (MST) From: "M. Warner Losh" <imp@bsdimp.com> To: phk@phk.freebsd.dk Cc: arch@FreeBSD.org Subject: Re: New "timeout" api, to replace callout Message-ID: <20071202.093603.228972203.imp@bsdimp.com> In-Reply-To: <19827.1196612123@critter.freebsd.dk> References: <20071202.085545.177225588.imp@bsdimp.com> <19827.1196612123@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20071202.093603.228972203.imp>