-
Notifications
You must be signed in to change notification settings - Fork 107
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
Ignore threads_per_core for unsupported machine types in vm-instance #382
Conversation
/gcbrun |
@kkr16 does this merit review now? Please edit the PR to target the |
No, @nick-stroud and I had a chat on the target behavior. I'll push a change accordingly.
Will do. Thanks! |
Please squash these commits as advised in #411 |
Done. Thanks! |
/gcbrun |
@kkr16, I just had a few "nits". For context, "nits" are suggestions that, in my opinion, would improve the code but are not required for my approval. It is your choice whether or not to accept these suggestions. If you want to decline the suggestions, then just respond "Ack." to the comment and resolve the thread. This just lets me know that you saw it and are not going to act on it. If you do make any of the suggested changes then I would just add it as one additional commit titled something like "Addressing feedback". Either way once you are done I will approve and merge. |
/gcbrun |
Description
Adds a condition to the
advanced_machine_features
block in thevm-instance
module that is used to bypass thethreads_per_core
parameter for machine types that do not support setting an SMT parameter (t2d instances, shared core instances, and instances with <2 vCPU).The default
threads_per_core
has been set to0
, which translates to an intelligent default behavior that turns off SMT on supported machine types, and removes the parameter where it is not supported.To test,
test_configs/threads_per_core.yaml
has been expanded to include more machine types, andthreads_per_core=null
, andthreads_per_core=0
.Submission Checklist
pre-commit install
)make tests
)