[asterisk-bugs] [Zaptel 0010314]: [patch] Merged in support for high resolution timers in kernel >=2.6.16
noreply at bugs.digium.com
noreply at bugs.digium.com
Tue Jul 31 11:36:00 CDT 2007
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=10314
======================================================================
Reported By: darren1713
Assigned To:
======================================================================
Project: Zaptel
Issue ID: 10314
Category: ztdummy
Reproducibility: always
Severity: feature
Priority: normal
Status: new
Zaptel Version: SVN
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!): 2770
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 07-26-2007 18:36 CDT
Last Modified: 07-31-2007 11:35 CDT
======================================================================
Summary: [patch] Merged in support for high resolution timers
in kernel >=2.6.16
Description:
The new high resolution timer in the kernel generates very accurate
periodic timing. Just using the kernel based timing gets these sorts of
results from ztdummy (99.999992% avg):
......
8192 samples in 8192.000000 sample intervals 100.000000%
8192 samples in 8192.008000 sample intervals 99.999908%
--- Results after 123 passes ---
Best: 100.000000 -- Worst: 99.999512 -- Average: 99.999992
The high resolution timer in ztdummy is only built if it's supported and
enabled in the kernel, and will continue to use the RTC timing if the high
resolution timers are not available.
Specifically, CONFIG_HIGH_RES_TIMERS needs to be enabled (Processor type
and features -> High Resolution Timer Support), and optionally, (Processor
type and features -> HPET Timer Support) provides a better clock source.
There should be no side effects to this, since it's the new kernel
timers.
Adding an option into the "make menuselect" to force RTC instead if they
are both available would be a good addition. Configs/Makefiles are not my
fortay, so this would be better for someone else to do.
======================================================================
----------------------------------------------------------------------
tzafrir - 07-31-07 11:35
----------------------------------------------------------------------
(sorry for the delayed reply.
actually printk_ratelimit gives you exactly that time-based rate
limiting.
It has more overhead than a simple test based on a static var, though.
http://lxr.linux.no/ident?i=printk_ratelimit
http://lxr.linux.no/source/kernel/printk.c#L1103
Issue History
Date Modified Username Field Change
======================================================================
07-31-07 11:35 tzafrir Note Added: 0068141
======================================================================
More information about the asterisk-bugs
mailing list