Adjust snt < max_cpu calculation #14280
Open
+14
−3
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.
[Bug #20146]
Previously we dealt with the main Ractor not being enabled for M:N by incrementing
snt_cnt++
. This worked for comparing against ractor count, but meant that we always had one less SNT than was specified byRUBY_MAX_CPU
.This was notably a problem for
RUBY_MAX_CPU=1
, which would cause Ractors to hang.This commit instead of adjusting snt, adjusts a "
schedulable_ractor_cnt
". This waysnt_cnt
will actually reachRUBY_MAX_CPU
.