You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@mynewt.apache.org by "Sheela (JIRA)" <ji...@apache.org> on 2017/08/17 20:11:00 UTC

[jira] [Updated] (MYNEWT-97) If a slave is applying slave latency on a connection and gets handed a packet it should send it ASAP

     [ https://issues.apache.org/jira/browse/MYNEWT-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sheela updated MYNEWT-97:
-------------------------
    Fix Version/s:     (was: v1_2_0_rel)
                   v1_3_0_rel

> If a slave is applying slave latency on a connection and gets handed a packet it should send it ASAP
> ----------------------------------------------------------------------------------------------------
>
>                 Key: MYNEWT-97
>                 URL: https://issues.apache.org/jira/browse/MYNEWT-97
>             Project: Mynewt
>          Issue Type: Improvement
>      Security Level: Public(Viewable by anyone) 
>            Reporter: William San Filippo
>            Assignee: William San Filippo
>            Priority: Minor
>              Labels: controller
>             Fix For: v1_3_0_rel
>
>
> The current controller code applies slave latency even if there are packets on its transmit queue. If there are packets on the controller queue, the host has the MD (more data) bit set or, while applying slave latency, gets a packet handed to that connection by the host, the controller should stop using slave latency and wake up on the next connection event instead of applying latency.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)