PetervdPerk-NXP commented on PR #17358: URL: https://github.com/apache/nuttx/pull/17358#issuecomment-3724638066
> @PetervdPerk-NXP this was already an issue with NuttX 10.3.0 but it seems like it only manifest under certain conditions / network pressure. This ticket & PR were opened by @mennovf because we are hitting this issue with current PX4 for our custom board. See [PX4/PX4-Autopilot#25956](https://github.com/PX4/PX4-Autopilot/issues/25956) > > NuttX 12.12 might make the conditions to trigger this easier, but it was definitely an issue before. Surely but with 10.3.0 atleast IOB could get full and not deadlock this easily, right now the first occurence of a full with IOB with TCP traffic yields a deadlock for me, This is most likely more logical/state machine problem. NuttX 10.3.0 working fine with this config ``` CONFIG_IOB_NBUFFERS=24 CONFIG_IOB_BUFSIZE=196 CONFIG_IOB_THROTTLE=0 ``` NuttX 12.12.0 config needed to avoid deadlocks ``` CONFIG_IOB_NBUFFERS=256 CONFIG_IOB_BUFSIZE=256 CONFIG_IOB_THROTTLE=0 ``` Overall, the throughput appears quite inconsistent, even though the CPU load remains relatively low at around 6% from the thread generating the TCP data. I understand that @xiaoxiang781216 and his team have been working on rewriting the NET/IOB stack for several years, but I was expecting performance improvements rather than a regression. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
