improve real-time documentation, find coding conventions

[kaspar030]

While it is certainly possible to create real-time applications with RIOT, depending on the definition and requirements, actual documentation and coding conventions are lacking.

We should come up with

a) conventions like "disabling IRQ's for less than N instructions is tolerable" (example)
b) document side effects caused by a)
c) document algorithmic implications on real-time requirements (e.g., "locking a mutex might traverse the list of currently locked threads")

...

[LudwigKnuepfer]

Maybe it's more purposeful to provide some tool for the task of identifying the possible side-effects anyways.

[kaspar030]

Maybe it's more purposeful to provide some tool for the task of identifying the possible side-effects anyways.

Interesting. You mean e.g., a static code analyzer beefed up to count critical section cycles?

[LudwigKnuepfer]

Something like that, yes.

[kYc0o]

any news on this? There's no milestone but a current issue is referencing this one, so maybe we need to put a milestone on this too.

[LudwigKnuepfer]

Do as you please.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want me to ignore this issue, please mark it with the "State: don't stale" label. Thank you for your contributions.

[kaspar030]

Not much discussion here.