thread_setaffinity: Allow affinity
param to have a length less than cpumask_size()
#652
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.
Instead of enforcing that the table length is
>= cpumask_size()
, any missing CPU numbers get assigned an affinity offalse
. This makes this API a bit more user-friendly, since users no longer have to initialize a table of lengthcpumask_size()
before setting the particular affinities they actually want.As an example, before this commit, you'd have to do something like:
But after this commit, this table:
will now be accepted and all the missing keys up to
uv_cpumask_size()
will be treated asfalse
in thethread_setaffinity
call.