You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@nuttx.apache.org by GitBox <gi...@apache.org> on 2021/12/30 14:21:27 UTC

[GitHub] [incubator-nuttx] xiaoxiang781216 commented on pull request #5104: net/tcp/udp: allocate tcp/udp connect dynamically

xiaoxiang781216 commented on pull request #5104:
URL: https://github.com/apache/incubator-nuttx/pull/5104#issuecomment-1003050437


   > What's the motivation for allocating the resources dynamically? The decision for this type of change should consider an analysis of the tradeoffs.
   
   To support the complex system better, we have saw in a production system:
   
   1. Application or server may create more socket in some special case
   2. New version may create more socket and then old config stop working
   3. TIME_WAIT state in TCP make the situation even worse:
       http://www.serverframework.com/asynchronousevents/2011/01/time-wait-and-its-design-implications-for-protocols-and-scalable-servers.html
   
   Yes, it's a tradeoff, but dynamic allocation already exist inside socket API before this patch.


-- 
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: commits-unsubscribe@nuttx.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org