Expose health table mutex publically #64

2026-01-08T19:51:00+01:00

tbaumgartl commented

2026-01-08 19:51:00 +01:00

Each health table get/set operation is mutex protected. The mutex timeout is relatively long- per default set to 20ms. When a user needs to read/write a lot of health states, this can be quite time intensive.
By exposing the mutex publically via a getter function, health table users may lock the mutex once with a custom timeout and then proceed with the usual get/set operations without a time penalty, since fsfw mutex supports recursive locking (mutex doesn't need to be locked twice by the same task).

Each health table get/set operation is mutex protected. The mutex timeout is relatively long- per default set to 20ms. When a user needs to read/write a lot of health states, this can be quite time intensive. By exposing the mutex publically via a getter function, health table users may lock the mutex once with a custom timeout and then proceed with the usual get/set operations without a time penalty, since fsfw mutex supports recursive locking (mutex doesn't need to be locked twice by the same task).

tbaumgartl added 1 commit 2026-01-08 19:51:00 +01:00

Expose health table mutex publically 4c3c93c106

tbaumgartl requested review from muellerr 2026-01-08 19:51:00 +01:00

muellerr merged commit cceef62cb6 into main

2026-01-09 13:34:10 +01:00

muellerr deleted branch baumgartl/expose-healthtable-mutex

2026-01-09 13:34:10 +01:00

muellerr referenced this issue from a commit

2026-01-09 13:34:11 +01:00

Merge pull request 'Expose health table mutex publically' (#64) from baumgartl/expose-healthtable-mutex into main

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: KSat/fsfw#64