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

[Simon Goldschmidt]

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

> With a mutex and condition variable instead of a semaphore, you can
interlock more nicely with the tcpip thread.

You can do that with a semaphore that is used as a binary semaphore, don't
you? Why the condition variable _and_ mutex?

> That's hard now without things like SYS_ARCH_PROTECT (which just acts like
a really large mutex). These would be per-connection, not per-thread though.
But it would more nicely solve the send/recv safety issue.

But per-connection would make the mutex be used by 2 threads again, how would
you solve this?

I see the semaphore as a global event -> tcpip_thread has finished processing
my request. And for that, you only need one semaphore per thread.

    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Nachricht geschickt von/durch Savannah
  http://savannah.nongnu.org/