Revisit SMP Locking of core data structures #1128
Labels
No labels
UX
active development
backlog
blocker
bootstrap
bounty
bug
dependencies
discussion
documentation
duplicate
enhancement
flaky test
help wanted
invalid
javascript
question
release
tendentious
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
mighty-gerbils/gerbil#1128
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We have some core data structures in the runtime that are protected by spin locks.
The rationale for this is that they are virtually free (compared to mutexes) in UP, and workable in SMP as they tend to be fast but busy wasting power depending on contention. With low contention they are very performant, but with high contention they are power hungry.
This is an acceptable trade off for now, where SMP is still WIP, but when it's time for production we'll need a more coherent locking strategy. I would love to see some form of futex, so that we can avoid the overhead of full blown mutexes and still protect critical structures without using too much power.