You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@mynewt.apache.org by "Aditi Hilbert (JIRA)" <ji...@apache.org> on 2018/02/06 07:39:00 UTC

[jira] [Updated] (MYNEWT-100) Improved mbuf usage by the controller

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

Aditi Hilbert updated MYNEWT-100:
---------------------------------
    Labels: NimBLE controller  (was: controller)

> Improved mbuf usage by the controller
> -------------------------------------
>
>                 Key: MYNEWT-100
>                 URL: https://issues.apache.org/jira/browse/MYNEWT-100
>             Project: Mynewt
>          Issue Type: Improvement
>      Security Level: Public(Viewable by anyone) 
>          Components: Nimble
>    Affects Versions: v0_8_0_beta1
>            Reporter: William San Filippo
>            Assignee: William San Filippo
>            Priority: Major
>              Labels: NimBLE, controller
>             Fix For: WISHLIST
>
>
> The current controller code can be improved by modifying how it uses mbufs. Currently, the code grabs an mbuf for advertising and scanning and never releases it. Furthermore, the controller uses an empty pdu per connection (it is in the connection state machine structure) and also allocates mbufs (from the msys pool) for LL control procedures. It would be better if the controller either had its own smaller pool of mbufs or simply had one mbuf allocated per connection as there will only be one control pdu or empty pdu outstanding at any given time (per connection).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)