You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@mynewt.apache.org by "Łukasz Rymanowski (JIRA)" <ji...@apache.org> on 2017/11/17 10:10:00 UTC

[jira] [Commented] (MYNEWT-799) Improve buffer size for events in the controller code

    [ https://issues.apache.org/jira/browse/MYNEWT-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16256778#comment-16256778 ] 

Łukasz Rymanowski commented on MYNEWT-799:
------------------------------------------

Make use of Event_type.data_status in LE Extendede Advertising Report Event  and basically send multiple events if buffer is too small.

> Improve buffer size for events in the controller code
> -----------------------------------------------------
>
>                 Key: MYNEWT-799
>                 URL: https://issues.apache.org/jira/browse/MYNEWT-799
>             Project: Mynewt
>          Issue Type: Improvement
>      Security Level: Public(Viewable by anyone) 
>          Components: Nimble
>            Reporter: Łukasz Rymanowski
>            Assignee: Łukasz Rymanowski
>            Priority: Minor
>             Fix For: v1_4_0_rel
>
>
> For Bluetooth 5 controller might need bigger buffer to transport e.g. extended advertising report to the host. As for now there are two mempools in the controller used for events. One for high prio events and second for low prio events. Both uses same hardcoded block size which for Bluetooth 5 is quite big.
> In this patch we should review that code and improve it.
> This Jira came up after discussion on this PR:
> https://github.com/apache/mynewt-core/pull/378#pullrequestreview-48060201



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