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
[erts] Fix long signal delivery time for processes in dirty run queues
OTP-18841
Commit (1) changed so that signals sent to processes scheduled for dirty
execution didn't trigger rescheduling of such processes to normal schedulers
in order to handle signals, but instead rely on the dirty signal handler
processes to take care of handling the signals for such processes. This
since a steady flow of incoming signals to processes scheduled for dirty
execution caused such processes to bounce between schedulers and could
prevent them from making progress. The dirty signal handler processes did
however not take care of the signals until the receiving processes were
selected for execution. As a result of this, if a process got stuck for a
long time in a dirty run queue due to heavy usage of dirty schedulers, it
took a long time until signals were delivered to such processes. As of this
commit, dirty signal handler processes will also take care of signal handling
for processes in dirty run queues.
(1) 53b1983
0 commit comments