Context Navigation

Changes between Initial Version and Version 1 of Ticket #8007, comment 22

initial	v1
1	1	I am not really a fan of unconditional thread priority boost after acquiring a lock - we actually had such a system in place, once, but it didn't really work with our threading model. Maybe works better when we restrict it to mutexes, though, but I somehow doubt it; why should a low priority thread be able to preempt a high priority thread just because it acquired a mutex?
2	2
3		Priority inversion means that low priority threads are able to starve high priority threads by sharing the same lock - due to other system activity, the low priority thread doesn't get through with its work, so the high priority thread ~~somehow~~ inherits the low priority, thus it becomes a victim of priority inversion.
	3	Priority inversion means that low priority threads are able to starve high priority threads by sharing the same lock - due to other system activity, the low priority thread doesn't get through with its work, so the high priority thread effectively inherits the low priority, thus it becomes a victim of priority inversion.