On Sun, 29 Jul 2012, Alexander Motin wrote:
With ACPI timer gradually becoming one of slowest in the system, is there
some reason to use it directly in acpi_cpu_idle()? I've made a patch:
http://people.freebsd.org/~mav/sleep_time.patch
to use binuptime() instead. Using even HPET from system tim
On 29.07.2012 11:37, Bruce Evans wrote:
On Sun, 29 Jul 2012, Alexander Motin wrote:
With ACPI timer gradually becoming one of slowest in the system, is
there some reason to use it directly in acpi_cpu_idle()? I've made a
patch:
http://people.freebsd.org/~mav/sleep_time.patch
to use binuptime()
On Sun, 29 Jul 2012, Alexander Motin wrote:
On 29.07.2012 11:37, Bruce Evans wrote:
...
binuptime() is more accurate than uncalibrated scaling. Is accuracy
required?
Accuracy is not required at all. +-20% is not a problem.
If not, the CPU ticker might work, and is faster than HPET,
and and
On 29.07.2012 15:26, Bruce Evans wrote:
On Sun, 29 Jul 2012, Alexander Motin wrote:
On 29.07.2012 11:37, Bruce Evans wrote:
...
binuptime() is more accurate than uncalibrated scaling. Is accuracy
required?
Accuracy is not required at all. +-20% is not a problem.
If not, the CPU ticker mig
On Sun, 29 Jul 2012, Alexander Motin wrote:
On 29.07.2012 15:26, Bruce Evans wrote:
On Sun, 29 Jul 2012, Alexander Motin wrote:
On 29.07.2012 11:37, Bruce Evans wrote:
...
binuptime() is more accurate than uncalibrated scaling. Is accuracy
required?
Accuracy is not required at all. +-20%
On 30.07.2012 07:33, Bruce Evans wrote:
On Sun, 29 Jul 2012, Alexander Motin wrote:
On 29.07.2012 15:26, Bruce Evans wrote:
On Sun, 29 Jul 2012, Alexander Motin wrote:
On 29.07.2012 11:37, Bruce Evans wrote:
...
binuptime() is more accurate than uncalibrated scaling. Is accuracy
required?
