[asterisk-bugs] [JIRA] (DAHLIN-290) dahdi_dynamic_eth have a huge jitter on transmit
Pavel Selivanov (JIRA)
noreply at issues.asterisk.org
Wed Jan 16 07:00:45 CST 2013
[ https://issues.asterisk.org/jira/browse/DAHLIN-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=201608#comment-201608 ]
Pavel Selivanov commented on DAHLIN-290:
----------------------------------------
Any news on problem ?
Actually, I think it (workqueue or tasklet) should be moved to dahdi_dynamic.
dynamic already has tasklet.
dynamic should start tasklet on rx (default untill dahdi 2.6.x), on tx(will solve this bug), or not used at all.
We can set a flag in dahdi_dynamic_driver, irq_safe_tx (zero by default).
> dahdi_dynamic_eth have a huge jitter on transmit
> ------------------------------------------------
>
> Key: DAHLIN-290
> URL: https://issues.asterisk.org/jira/browse/DAHLIN-290
> Project: DAHDI-Linux
> Issue Type: Bug
> Security Level: None
> Components: dahdi_dynamic_eth
> Affects Versions: 2.6.1
> Environment: tasklets enabled in dahdi_dynamic.c (#define ENABLE_TASKLETS)
> Reporter: Pavel Selivanov
> Assignee: Pavel Selivanov
> Attachments: 0001-dahdi_dynamic-Use-a-tasklet-for-flushing-dynamic-dri.patch, 0002-Revert-dahdi_dynamic_eth-Move-tx-packet-flushing-to-.patch, dahdi_dynamic.c.patch, dahdi_dynamic_eth.c.patch
>
>
> At r10562 "Move tx packet flushing to process context".
> Seems, using a common "thread" can produce a huge jitter.
> Since this "common" thread can be used by any driver - it can't guarantee 1ms...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list