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

Add c4a to the nosmt list #3211

Merged
merged 1 commit into from
Nov 4, 2024
Merged

Conversation

linsword13
Copy link
Contributor

This fixes the issue where Slurm wrongly considers c4a to have smt enabled
(threads_per_core=2). In truth, smt is not applicable for Arm machines.

Test with the change:

 # As indicated from lscpu, c4a always has 1 thread per core
linsword_google_com@c4atest-c4ahighmemnode-0:~$ lscpu | grep "per "
Thread(s) per core: 1
Core(s) per socket: 72

 # Verify the number looks correct with the change
linsword_google_com@c4atest-login-001:~$ scontrol show nodes | grep 72 | head -n2
NodeName=c4atest-c4ahighmemnode-0 Arch=aarch64 CoresPerSocket=72
   CPUAlloc=0 CPUEfctv=72 CPUTot=72 CPULoad=0.06

This fixes the issue where Slurm wrongly considers c4a to have smt
enabled
(threads_per_core=2). In truth, smt is not applicable for Arm machines.

Test with the change:

```sh
 # As indicated from lscpu, c4a always has 1 thread per core
linsword_google_com@c4atest-c4ahighmemnode-0:~$ lscpu | grep "per "
Thread(s) per core: 1
Core(s) per socket: 72

 # Verify the number looks correct with the change
linsword_google_com@c4atest-login-001:~$ scontrol show nodes | grep 72 | head -n2
NodeName=c4atest-c4ahighmemnode-0 Arch=aarch64 CoresPerSocket=72
   CPUAlloc=0 CPUEfctv=72 CPUTot=72 CPULoad=0.06
```
@harshthakkar01
Copy link
Contributor

/gcbrun

@harshthakkar01 harshthakkar01 added the release-chore To not include into release notes label Nov 4, 2024
@mr0re1 mr0re1 assigned mr0re1 and unassigned harshthakkar01 Nov 4, 2024
@mr0re1 mr0re1 merged commit a25dc21 into GoogleCloudPlatform:develop Nov 4, 2024
8 of 57 checks passed
@rohitramu rohitramu mentioned this pull request Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-chore To not include into release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants