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
[RFE] Support for negation "^" in the cpulist_unpack function #49
Comments
@yarda - would like to know your inputs? |
Do you talk about isolated_cores settings in cpu-partitioning-variables.conf? If yes, I think we could add support for negation into cpulist_unpack or cpulist_present Tuned built-in functions. Maybe I would prefer '!' as negation, but it shouldn't be problem to support both syntaxes ('!' and '^'), e.g. the following: |
Ah, it's clear from the subj. I am for it. |
Thanks @yarda. I should be able to raise a pull request by next week. |
cpulist_unpack supports range, it would be good add negation support via ^ or !, inorder to exclude cpus from the specified range. Fixes redhat-performance#49
In OpenStack, some of the configuration support negation, like, having the cpu list as ["1-5", "^3"], should eventually add the list as "1,2,4,5". We have a scenario where we need to pass the same list of parameter to both OpenStack and tuned (tuned-profile-cpu-partitioning's isolated_cores).
The expansion can be added at the caller, and it has to be added in multiple places. If it is done in the tuned it would be nice to have feature and has consistency.
The text was updated successfully, but these errors were encountered: