Review Board 1.7.16

Various updates to the timing API

Review Request #162 - Created Feb. 16, 2009 and submitted

Russell Bryant
Now that we have multiple timing modules, only being to load one module is causing some usability issues.  So, that inspired this patch.  I am proposing that this patch go in both trunk and 1.6.1.

1) Add module use count handling so that timing modules can be unloaded.

2) Allow multiple timing modules to be loaded, and use the one with the highest priority value.

3) Report which timing module is being use in the "timing test" CLI command, at the request of Tzafrir on the -dev list.

Note: This patch requires the heap implementation from /r/160/.
It compiles.  "timing test" still works and reports the module I would expect to be in use.
Review request changed
Updated (Feb. 16, 2009, 4 a.m.)
Include minor documentation fixes
Ship it!
Posted (Feb. 16, 2009, 5:30 a.m.)
This looks fine, but will require the heap stuff to be added to 1.6.1 without the scheduler changes, as discussed on IRC. runs on a server provided by Digium, Inc. and uses bandwidth donated to the open source Asterisk community by API Digital Communications in Huntsville, AL USA.
Please report problems with this site to