[GitHub] [mynewt-nimble] andrzej-kaczmarek commented on issue #793: min\max_ce_len, how is it used internally?

[GitBox <gi...@apache.org>]

andrzej-kaczmarek commented on issue #793: min\max_ce_len, how is it used internally?
URL: https://github.com/apache/mynewt-nimble/issues/793#issuecomment-610263805
 
 
   NimBLE controller does not use min/max CE length parameters for scheduling but it does validate them (likely there was intention to use them, but it was never implemented).
   
   There's syscfg settings which affects connection event length, namely `BLE_LL_CONN_INIT_SLOTS`, which sets minimum number of slots allocated for each connection event. It usually does not affect limit the number of concurrent connections controller is able to support since it will just skip connection events it cannot schedule. When there are 2 colliding connection events, the least recently scheduled connection has priority (the other one is skipped and that connection moves to next connection event). So with multiple connections with short connection interval just make sure supervision timeouts are long enough so controller can skip connection events without timeouts happening.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services