| Summary: | DAHLIN-00277: Use monotonic clock for core timer | ||
| Reporter: | Shaun Ruffell (sruffell) | Labels: | |
| Date Opened: | 2012-01-23 09:57:56.000-0600 | Date Closed: | 2012-04-03 16:46:25 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | |
| Versions: | 2.5.0.2 2.6.0 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | DAHDI uses current_kernel_time() to calculate the number of milliseconds of audio to process when conferencing in the core timer. This makes DAHDI susceptible to large clock changes from NTP. DAHD currently works around this by not conferencing when there are large differences, but if the clock is constantly jumping around then it would still be possible for DAHDI to attempt to mix more audio for the conference than necessary. I believe switching this to the ktime_get_ts function will alleviate the need to use the wall time. This came up on the mailing list: http://thread.gmane.org/gmane.comp.telephony.pbx.asterisk.user/266461/focus=266523 | ||
| Comments: | By: Shaun Ruffell (sruffell) 2012-04-03 16:46:26.010-0500 Committed onto trunk in [r10482|http://svnview.digium.com/svn/dahdi?view=revision&revision=10482] and will be in the 2.7.0 release. | ||