Date: Mon, 31 Oct 2005 18:18:35 +0800 From: David Xu <davidxu@freebsd.org> To: Robert Watson <rwatson@freebsd.org> Cc: Alexander Leidinger <Alexander@Leidinger.net>, freebsd-current@freebsd.org Subject: Re: TSC instead of ACPI: powerd doesn't work anymore (to be expected?) Message-ID: <4365EF7B.1020706@freebsd.org> In-Reply-To: <20051031083447.Y11619@fledge.watson.org> References: <30595.1130493297@critter.freebsd.dk> <20051028153457.d0wqgn2ask4sgw4k@netchild.homeip.net> <20051029195703.GB39253@dragon.NUXI.org> <43646AAC.2080107@freebsd.org> <20051030093718.GE39253@dragon.NUXI.org> <4364D90F.3090205@samsco.org> <20051031075843.GF39253@dragon.NUXI.org> <20051031083447.Y11619@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Robert Watson wrote: > > > It has been suggested that the former can operate quite well with > significantly reduced quality. It has alos been suggested that most > applications could operate fine with somewhat reduced quality, but that > the API definitions don't say anything about how to specify application > quality requirements vs performance requirements for time measurement. Can we change gettimeofday and clock_gettime to lower resolution now? I think 1000hz/s is enough for most applications, since a thread can never sleep shorter than a tick for years. We can introduce hrtime_t clock_gethrtime(clockid_t clock) to get hi-resolution time as the one seen in RTLinux, or gethrtime() as seen in Solaris (Daniel Eischen said?) David Xu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4365EF7B.1020706>