Closed vyzo closed 4 months ago
Name | Link |
---|---|
Latest commit | 8808136afc57ed3487407d733ae7127dd90e542e |
Latest deploy log | https://app.netlify.com/sites/elastic-ritchie-8f47f9/deploys/65d472029dc6de000875d4ef |
Deploy Preview | https://deploy-preview-1126--elastic-ritchie-8f47f9.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
I think we should be using futexes or something else on Linux that doesn't busywait and waste batteries on laptop smpβand importantly, this should be all abstracted over somehow in a macro.
If you want this in, fine for now, but then you should open an issue about getting locking right on SMP.
It is abstracted over a macro, see __lock-inline!
and __unlock-inline!
.
It is a workable solution for SMP, the critical sections are expected to be small (less than 10ns each) so the spin/busy wait is not that bad.
Ideally we'd have futexes; unfortunately full gambit mutexes are so much slower it is not even funny.
Follow up issue in #1128.
This changes the prototype table lock to be a spin lock .... and it is almost 3x faster.
Before:
After: