[
https://issues.apache.org/jira/browse/MYNEWT-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15392319#comment-15392319
]
ASF subversion and git services commented on MYNEWT-83:
-------------------------------------------------------
Commit 0888ff9aace82f300fe3900db9358b57f551a01d in incubator-mynewt-core's
branch refs/heads/phyrx_no_mbuf from [~wes3]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=0888ff9
]
MYNEWT-83: Use a fixed buffer for reception for controller stack
The nimble stack was using mbufs for reception and now uses a
static buffer. The reason behind the change is that we wanted
to be able to receive a frame even though no mbufs were available.
This would allow transmit packets to receive ACKs and thus free
up transmit buffers waiting on connection queues.
There were a number of code changes associated with the phy API.
Implemented a more efficient copy routine to copy words from
the static rx buffer into mbufs. Note that this is not yet done
for transmit frames as we are not sure we could guarantee that
the data pointer is aligned.
> Controller should use a fixed buffer for reception as opposed to mbufs
> ----------------------------------------------------------------------
>
> Key: MYNEWT-83
> URL: https://issues.apache.org/jira/browse/MYNEWT-83
> Project: Mynewt
> Issue Type: Improvement
> Components: Nimble
> Affects Versions: v0_8_0_beta1
> Reporter: William San Filippo
> Assignee: William San Filippo
> Priority: Minor
> Fix For: v0_10_0
>
>
> The current controller code allocates mbufs for reception. During the
> unplugfest it was noted that is was fairly easy to overload the
> host/controller with packets. A probably better way to implement this is to
> have a global receive buffer and we copy out into a mbuf if needed. Note that
> the transmit portion of the controller already uses a global buffer for
> transmission.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
