You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original bug ID: 2800 Reporter: administrator Status: closed Resolution: won't fix Priority: normal Severity: feature Category: ~DO NOT USE (was: OCaml general)
Bug description
Hi,
I have just seen that module Mutex does not wake up threads in the order
they tried to lock a mutex. I have an application that uses timeouts to
terminate certain operations that take too long. That's why FIFO-order
would be extremely helpful, because the thread that needs the protected
resource most urgently is usually the first in the queue. Would it,
please, be possible to improve the Mutex-implementation?
Original bug ID: 2800
Reporter: administrator
Status: closed
Resolution: won't fix
Priority: normal
Severity: feature
Category: ~DO NOT USE (was: OCaml general)
Bug description
Hi,
I have just seen that module Mutex does not wake up threads in the order
they tried to lock a mutex. I have an application that uses timeouts to
terminate certain operations that take too long. That's why FIFO-order
would be extremely helpful, because the thread that needs the protected
resource most urgently is usually the first in the queue. Would it,
please, be possible to improve the Mutex-implementation?
Best regards,
Markus
--
Markus Mottl http://www.oefai.at/~markus markus@oefai.at
The text was updated successfully, but these errors were encountered: