a-lunev commented on pull request #4659:
URL: https://github.com/apache/incubator-nuttx/pull/4659#issuecomment-962528759


   > > > > > btw, it has been on my todo list to remove CONFIG_NET_TCP_SPLIT. 
if it helps your work, please let me know. it isn't urgent and i don't want to 
interfere you by submitting conflicting patches.
   > > > > 
   > > > > 
   > > > > Oh, really? I do not personally need CONFIG_NET_TCP_SPLIT algorithm. 
What about others? Is there any previous discussion about its deletion? I'm not 
sure, if there is a reason to preserve it? If I understand correctly, 
CONFIG_NET_TCP_SPLIT was developed for MCUs with tiny memories that do not have 
enough memory for a sufficient TCP retransmission queue depth.
   > > > 
   > > > 
   > > > it's just my personal todo. not community's. while i can understand 
the motivation, it doesn't work well even with a traditional tcp stack.
   > > 
   > > 
   > > Can we poll NuttX developers about CONFIG_NET_TCP_SPLIT deletion? As I 
said, I personally do not need it. However, I'm afraid of if someone still 
needs CONFIG_NET_TCP_SPLIT?
   > 
   > it's a valid concern. i posted it on the ML. 
https://www.mail-archive.com/dev@nuttx.apache.org/msg07045.html
   
   @yamt as PR #4660 is already merged into the master branch, I have adapted 
my patch to the removed NET_TCP_SPLIT option.


-- 
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-unsubscr...@nuttx.apache.org

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


Reply via email to