kamkow1/www.kamkow1lair.pl
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

biglock edit 1
All checks were successful
Build website / build-and-deploy (push) Successful in 3m45s
Details

Browse Source
This commit is contained in:
Kamil Kowalczyk
2026-04-27 21:06:49 +02:00
parent 4942a77307
commit a5fb6bb942
1 changed files with 13 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
content/blog/MOP2/biglock.adoc
View File

@@ -230,3 +230,16 @@ affect the system, because of it's premises - being a hobby OS and lacking sophi
better performance/control.
Hope you've learned something useful about big locks vs. fine-grained locks!
== EDIT 1
Funnily enough, after some testing and playing around with the system, I've found that the big lock actually has improved
performance significantly?
Why?
I think it's due to previously having a lot of spin locks, which equate to a huge amount of atomic reads/writes. Such
operations on x86 may cause a performance problem, because they have to be synced across all cores. Having a big lock
once on entry and big unlock on exit reduces the amount of these operations. That's just speculation, I don't have
any real _numbers_ to back this up; it's all based on anecdotal **feel** of the system, while using it and running
test apps.