[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-devel] [patch #5960] Enable multithread send/recv operations on sa

From: Simon Goldschmidt
Subject: [lwip-devel] [patch #5960] Enable multithread send/recv operations on same socket on TCP netconns
Date: Wed, 23 May 2007 14:48:24 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv: Gecko/20070309 Firefox/

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:


  Nachricht geschickt von/durch Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]