[riot-notifications] [RIOT-OS/RIOT] cpu/esp_common: esp_now netdev problems (#10682)

Gunar Schorcht notifications at github.com
Wed Jan 2 15:32:28 CET 2019


> > * We don't have any option to use `msg_try_send` instead of `msg_send`.
> 
> Might be a good idea to change that to a `msg_try_send()`. But this doesn't fix the problem of the filling ringbuffer of course :-/.

@miri64 It would help to use `msg_try_send()` if https://github.com/RIOT-OS/RIOT/blob/d3f78a5a4008a640ce4ad24743c77bfdc97c7730/sys/net/gnrc/netif/gnrc_netif.c#L1358 would return an error if `msg_try_send` failed. In that case, the caller would be able to decide what to do independent on whether it is done in interrupt or thread context. In our case, for example, it would probably be better to drop the new frame than to block the thread which is handling WiFi hardware events.

I'm wondering if it's not also a problem for other `netdev` drivers and what they do if the ISR event gets lost because they don't receive any feedback.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/issues/10682#issuecomment-450877699
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190102/4e25debe/attachment.html>


More information about the notifications mailing list