lwip-devel
[Top][All Lists]
Advanced

[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: Wed, 23 May 2007 10:44:54 +0000
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3

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

                 Summary: Enable multithread send/recv operations on same
socket on TCP netconns
                 Project: lwIP - A Lightweight TCP/IP stack
            Submitted by: fbernon
            Submitted on: mercredi 23.05.2007 à 12:44
                Category: None
                Priority: 5 - Normal
                  Status: None
                 Privacy: Public
             Assigned to: None
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any

    _______________________________________________________

Details:

Currently, with UDP connections, you can sendto and recvfrom datagrams with
two threads (one read, the other write). You can't do two reads in the same
times, but it's not a usual case. You could do two sends in the same time,
but there is a problem with current tcpip_thread api, because the
tcpip_thread can't know which task will fetch the message (and will be wake
up). More, about TCP, it's not possible to have a thread who read and another
who write (to implement full duplex protocols)...

Doing something clean should need to be have to have a semaphore "per thread"
to set in the api_msg struct...

See https://savannah.nongnu.org/task/?6683, comment#3, comment#4, and
comment#5...




    _______________________________________________________

Reply to this item at:

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

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





reply via email to

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