You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@mynewt.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/09/13 15:46:21 UTC
[jira] [Commented] (MYNEWT-387) Separate ACL data buffer pool for
controller-only nimble stack
[ https://issues.apache.org/jira/browse/MYNEWT-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15487567#comment-15487567 ]
ASF subversion and git services commented on MYNEWT-387:
--------------------------------------------------------
Commit 0fa968e2db3f18442ee417affb9fe2105c6f4b09 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=0fa968e ]
MYNEWT-387: Separate ACL buffer pool for controller only
The controller (for the controller only implementation) now uses
a separate pool of buffers for ACL data. This pool is only used
by the host to send ACL data; the controller will never grab a
buffer from this pool for any other reason. This was done so that
the controller and host will stay in sync regarding reported
total ACL buffers and the number of completed packets. By default,
4 ACL buffers are allocated. This is quite an arbitrary number
and should be modified based on memory available and application
requirements.
> Separate ACL data buffer pool for controller-only nimble stack
> --------------------------------------------------------------
>
> Key: MYNEWT-387
> URL: https://issues.apache.org/jira/browse/MYNEWT-387
> Project: Mynewt
> Issue Type: Bug
> Components: Nimble
> Affects Versions: v0_9_0
> Reporter: William San Filippo
> Assignee: William San Filippo
> Fix For: v1_0_0_beta1
>
>
> The controller-only nimble stack implementation could use ACL data buffers that were allocated to the host for other purposes. This could cause the host to think it could send an ACL data buffer when it fact it could not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)