[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: Frédéric Bernon
Subject: [lwip-devel] [patch #5960] Enable multithread send/recv operations on same socket on TCP netconns
Date: Tue, 29 May 2007 12:55:36 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv: Gecko/20070309 Firefox/

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

Some answers are in comment#31:

>Where would you add the sys_sem_signal(apimsg->msg.conn->apisem)?
"in "tcpip.c", lock the connection to protect concurrent access in
"tcpip_apimsg()", adding a sys_sem_wait(apimsg->msg.conn->apisem) and a

>When/How would it be initialized?
in netconn_new_with_proto_and_callback(), if LWIP_API_MULTITHREAD_PROT=1

>Would it be one apisem for all netconns or one per thread? (if one per
netconn, that would be the same as what we have now, wouldn't it?)
it's one per connection(netconn), but I don't understand "would be the same
as what we have now"? Which one? "sys_sem_t sem;" in "struct netconn"? It
it's this one, it is not used for that (I suppose it's mainly used in "write"
and "close" to avoid to consumne cycles to check a state).


Reply to this item at:


  Message posté via/par Savannah

reply via email to

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