[riot-notifications] [RIOT-OS/RIOT] Proposal: eSAUL - Extended Sensor Actuator Uber Layer (#14121)

chrysn notifications at github.com
Tue May 26 15:22:39 CEST 2020

> These callbacks are called in the context of the eSAUL thread and may send a message, wake-up a thread, ...

Yes. (Although that's not what sock_async does -- that only ever has one callback. The linked list would be an extension of that theme to also carry a next pointer to make the LL)

> I don't understand the semantic difference you see.

The semantic difference is that a message can get lost (of two distinct messages, only the first is processed if there is overflow), whereas an event always gets set but it's just indistinguishable whether it was set once or multiple times. That makes a difference when a process waits for multiple notifications (say, three temperature sensor readings fill up the queue and the humidity reading gets lost) or when there is data associated with the messages (which can't be in the event case).

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20200526/8d5e8083/attachment.htm>

More information about the notifications mailing list