zhhyu7 commented on PR #18211: URL: https://github.com/apache/nuttx/pull/18211#issuecomment-3822699747
> @zhhyu7 I have questions regarding this change. Bear in mind I'm not too familiar with the network stack. > > Those questions revolve around my tests using Espressif devices and WiFi. > > * From this change, it seems I need to set `CONFIG_NET_RECV_BUFSIZE` and `CONFIG_NET_SEND_BUFSIZE`. If I keep them at the default value of 0, it does no work anymore. Why is that? Should every device be modified now and what does the 0 value mean? > * Do you have any suggestions on how to orchestrate the IOB options to `NET_RECV_BUFSIZE` and `NET_SEND_BUFSIZE`? > My current approach is to calculate the number of IOBs to match `NET_RECV_BUFSIZE` + `NET_SEND_BUFSIZE`, given that each IOB has a fixed size (128 for instance, or 196 on many other devices). Does it make sense? > Example: > > ``` > CONFIG_IOB_BUFSIZE=128 > CONFIG_IOB_NBUFFERS=256 > CONFIG_IOB_NCHAINS=32 > CONFIG_IOB_THROTTLE=24 > CONFIG_NET_RECV_BUFSIZE=16384 > CONFIG_NET_SEND_BUFSIZE=16384 > ``` > > If I take those values: ` 16384 + 16384 = 128 * 256`. So that is how I am matching them and seems to work for ESP32-C3, so far. @fdcavalcanti Get! The latest version has reverted a modification that might have caused the sent message to be too small, and the previous issue was caused by this reason. In the TCP sending process, if our CONFIG_NET_SEND_BUFSIZE is set to 0, we need to ensure that CONFIG_IOB_THROTTLE * CONFIG_IOB_BUFSIZE > TCP_MSS (or CONFIG_NET_ETH_PKTSIZE - 54), otherwise the protocol stack will freeze. -- 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]
