[lwip-devel] [task #6994] Redesign Socket Layer with LWIP_TCPIP_CORE_LOCKING

[piero]

Follow-up Comment #19, task #6994 (project lwip):

i had a quick lock to socket2.c code...

just a suggest:

i saw that more function block forever with LOCK_TCPIP_CORE() if another task
is locking the core. So, if i have more tha one task, and each task try to
send a packet to different socket, each task can block until another free the
core. I want to suggest the possibility to call socket functions with a
timeout (it could be a define or related to some socket option, for example if
non-blocking socket is used), so, function should return with error COREBUSY,
and application can manage this error avoiding blocking (if the developer
wants this feature). It could be useful (but i'm not sure) if different tasks
will try to send to the SAME socket in the SAME moment: tasks should block
waiting their timeslot in lwip core, or return immediately and allow to
application to manage this situation.

Any comment?
Bye
Piero

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/task/?6994>

_______________________________________________
  Messaggio inviato con/da Savannah
  http://savannah.nongnu.org/