Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: use allowed cpus from target container #119

Merged
merged 1 commit into from
Feb 5, 2025

Conversation

joshiste
Copy link
Member

@joshiste joshiste commented Feb 5, 2025

if a process is limited to a certain cpuset or
some of the configured processors are not online, we need to pass the number of workers to stress-ng as otherwise stress-ng will always use the configured number of processors.

@joshiste joshiste force-pushed the fix/only_use_available_processors branch from c6318b1 to b94353d Compare February 5, 2025 15:57
if a process is limited to a certain cpuset or
some of the configured processors are not online, we
need to pass the number of workers to stress-ng as
otherwise stress-ng will always use the configured
number of processors.
@joshiste joshiste force-pushed the fix/only_use_available_processors branch from b94353d to 8e9fe47 Compare February 5, 2025 15:58
@joshiste joshiste enabled auto-merge February 5, 2025 15:59
@joshiste joshiste merged commit fa4d8a6 into main Feb 5, 2025
12 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Feb 5, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant