[asterisk-bugs] [JIRA] (DAHLIN-290) dahdi_dynamic_eth have a huge jitter on transmit

[Shaun Ruffell (JIRA)]

    [ https://issues.asterisk.org/jira/browse/DAHLIN-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=201622#comment-201622 ] 

Shaun Ruffell commented on DAHLIN-290:
--------------------------------------

I believe this issue is addressed in [(f44b252472ad "dahdi_dynamic: Use a tasklet for flushing dynamic drivers.")|http://git.asterisk.org/gitweb/?p=dahdi/linux.git;a=commitdiff;h=f44b252472ad76c87b682d56e2d603aba751fb29] and [(ef065a5e2a "Revert "dahdi_dynamic_eth: Move tx packet flushing to process context.")|http://git.asterisk.org/gitweb/?p=dahdi/linux.git;a=commitdiff;h=ef065a5e2a26ba7bc9c9c15158e7f38445f3523f].  Do you still have the same issues with the master branch of DAHDI?   

DAHDI-Linux has switched to git for the primary source control, so you can grab it like:

{{git clone git://git.asterisk.org/dahdi/linux dahdi-linux}}
                
> 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