[lwip-devel] [patch #5960] Enable multithread send/recv operations on same socket on TCP netconns

[Frédéric Bernon]

Follow-up Comment #34, patch #5960 (project lwip):

About comment#32, I think there is no risk with a patch like this, even for
netconn_write (where the problem is more on the RX side, with the
"tcp_sndbuf", but here, only one thread write). The main problem is to avoid
that task1 fetch a msg posted in answer of an action to task2. Note unlike
you said, it will not "protect the core stack", but only the connection (the
apisem is only in struct netconn).

Because I would like to support full duplex protocols, and because the patch
is small and can be disabled, I would like to integrate this feature...

About comment#33, even if I have provide some results about a possible new
design for sequential api in http://savannah.nongnu.org/task/?6935, I would
like first "terminate" potentials problems with current one...

Agree to check in ?


    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/patch/?5960>

_______________________________________________
  Message posté via/par Savannah
  http://savannah.nongnu.org/