[lwip-devel] [task #6683] Document lwIPs thread safety requirements

[Jonathan Larmour]

Follow-up Comment #10, task #6683 (project lwip):

>> Raw-API only (NO_SYS=1), network interfaces work with interrupts
> 
> Can this really work? netif->input may not be called from interrupt
context,
> since this might re.enter functions which are not re-entrant (tcp!). So
the
> only thing we can do would be freeing pbufs after sending (e.g. with a
> DMA-ethernetif that calls pbuf_ref() before sending).

I think it can work. Every raw API program needs some sort of loop or similar
to sit there waiting for events such as incoming packets to happen. An
interrupt routine could put pbufs in some form of queue (not necessarily an
lwip pbuf queue) and the main loop could pass them into lwip. Well, I think
anyway,

Jifl


    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/