Rename "deadlock" to "stall" in LoadManager
#5341
Open
+45
−46
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
High Level Overview of Change
In the condition of severe CPU starvation,
LoadManager
will intentionally crashrippled
reportingLogicError: Deadlock detected
. This error message is misleading; the condition being detected is not a deadlock. Let's change the name accordingly.Context of Change
In the context of multithreaded programs, 'deadlock' has a specific meaning and what the
LoadManager
class does, has nothing to do with it. At the time when this class was originally written,std::mutex
etc. primitives were unable to report actual deadlocks, so this classLoadManager
was used instead to detect a lack of progress inJobQueue
.Since then we have better tools, and the only thing this class is left doing is stall detection, which is not the same as deadlock detection.
Type of Change
.gitignore
, formatting, dropping support for older tooling)