RE : RE : [lwip-users] Some Help Needed Please

[Frédéric BERNON]

>Really? Both netconn_recv() and netconn_send() call api_msg_post() which pends 
>on conn->mbox,
>and that conn (& mbox) is the same for both threads. So when tcpip_thread 
>posts to that mbox,
>it's unknown which call (recv or send) has finished.

If it's true for TCP, it's wrong for UDP & RAW: netconn_recv in UDP just fetch 
a "buf" from recvmbox, that why I have precise "for sendto/recvfrom in UDP" in 
my answer...

But like we have talk in https://savannah.nongnu.org/task/?6683, comment #3, 
#4, #5, there is some solutions about that...
 
  
====================================
Frédéric BERNON 
HYMATOM SA 
Chef de projet informatique 
Microsoft Certified Professional 
Tél. : +33 (0)4-67-87-61-10 
Fax. : +33 (0)4-67-70-85-44 
Email : address@hidden 
Web Site : http://www.hymatom.fr 
====================================
P Avant d'imprimer, penser à l'environnement
 


-----Message d'origine-----
De : address@hidden [mailto:address@hidden De la part de Goldschmidt Simon
Envoyé : vendredi 11 mai 2007 08:18
À : Mailing list for lwIP users
Objet : RE: RE : [lwip-users] Some Help Needed Please




> 3/ I'm agree with Kieran, you can use the same socket to send
> and recv (lwIP is not already "thread-safe", but if I think 
> this is not a problem for sendto/recvfrom in UDP, I'm not so 

Really? Both netconn_recv() and netconn_send() call api_msg_post() which pends 
on conn->mbox, and that conn (& mbox) is the same for both threads. So when 
tcpip_thread posts to that mbox, it's unknown which call (recv or
send) has finished.

> sure for "select"). You can also use another socket to send,
> but don't bind it to 1900/udp...


Simon


_______________________________________________
lwip-users mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/lwip-users

Frédéric BERNON.vcf
Description: Frédéric BERNON.vcf