[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lwip-users] NO_SYS, TCP/IP and sockets
From: |
Simon Goldschmidt |
Subject: |
Re: [lwip-users] NO_SYS, TCP/IP and sockets |
Date: |
Wed, 16 Jan 2013 15:25:01 +0100 |
Fabian Cenedese wrote:
> >No. It's in the nature of BSD-alike socket APIs that they run
> "sequential". lwIP needs a dedicated thread to handle incoming packets and
> timers.
>
> I thought this would also be done from the polling thread.
>From which polling thread? I don't think I understand that...
> How should it be done now? Should my interrupt handler call
> myethif_input (which calls low_level_input) and give the received
> data to netif->input (which is tcpip_input)?
Yes. Your ethernet RX interrupt can allocate PBUF_POOL pbufs in the ISR and
call netif->input() (as long as that is tcpip_input). Everything is thread-safe
in this way (as long as you have set up SYS_LIGHTWEITH_PROT correctly).
Simon