[
https://issues.apache.org/jira/browse/MYNEWT-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15658640#comment-15658640
]
ASF subversion and git services commented on MYNEWT-336:
--------------------------------------------------------
Commit de4784827da2128a4bbec78397a986ff9c0a3773 in incubator-mynewt-core's
branch refs/heads/develop from [~wes3]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=de47848
]
MYNEWT-336: Allow for smaller mbufs in nimble.
The controller should now support the usage of smaller mbufs.
Please read the Jira ticket for more information regarding mbuf
usage by the controller and nimble. The major change associated
with this commit was fixing a routine that was called when data
packets where enqueued to a connection. The code was assuming
that all the data was in one mbuf and was overwriting the first
mbuf in the chain with the total mbuf chain length (the packet
header length). Also modified the bletest code to create chained
mbufs if the total packet length being sent exceeded a single mbuf.
> Allow smaller mbufs for data frames
> -----------------------------------
>
> Key: MYNEWT-336
> URL: https://issues.apache.org/jira/browse/MYNEWT-336
> Project: Mynewt
> Issue Type: Improvement
> Components: Nimble
> Reporter: Christopher Collins
> Assignee: William San Filippo
> Fix For: v1_1_beta1
>
>
> When the host sends a data packet, it fills an mbuf with the payload and
> passes it to the controller.
> The controller expects the mbuf to consist of a single contiguous buffer. To
> support this requirement, a nimble application needs to allocate large mbufs
> (>= 260 bytes) to permit large data packets to be sent. This is wasteful
> because many data frames are likely quite a bit smaller than this.
> Reliability would improve if an application could allocate more, smaller,
> mbufs.
> The fix is for the controller to accept mbufs that consist of several chained
> buffers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
