haukepetersen commented on issue #477: npl/riot: reduce default MSYS_1_BLOCK_SIZE to minimum URL: https://github.com/apache/mynewt-nimble/pull/477#issuecomment-507211954 Just gave this some tests using RIOTs `examples/nimble_gatt` example application, using the Nordic `nRF connect` Android app as GATT client. I deployed it on two different targets, `nrf52dk` and `microbit (nrf51)`. The bare minimum numbers, for which the GATT server was still working were - `MYNEWT_VAL_MSYS_1_BLOCK_SIZE := 77` - `MYNEWT_VAL_MSYS_1_BLOCK_COUNT := 4` For any block-size smaller than `77 bytes` I can't connect to the GATT server, so there must be something still missing in the numbers above?! For any block count <4 the phone can not connect to the device. I tried to figure out why 4 buffers are needed, but I am unsure. So in the most busy case, I get: - 1 mbuf allocated by the controller to receive the next packet - 1 mbuf allocated by the controller for keeping an empty packet to reply on the next connection event in case there is no GATT payload to be send - 1 mbuf holding data currently processed by the GATT server - 1 mbuf allocated by the GATT server for sending a reply?
---------------------------------------------------------------- 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: us...@infra.apache.org With regards, Apache Git Services
