I have a system running a financial trading application at a remote facility. I do not have access to the ILO/DRAC, but need to disable hyperthreading. The system runs Intel Westmere 3.33GHz X5680 hex-core CPUs. I can reboot, but want to make sure that the system does not enable hyperthreading due to performance problems. Is there a clean way to do this from within Linux?
Edit: The noht directive added to the kernel boot command line did not work. Same for RHEL.
Newer Kernels provide a Simultaneous Multithreading (SMT) control.
You can check the state of SMT with;
cat /sys/devices/system/cpu/smt/active
Change the state with
echo off > /sys/devices/system/cpu/smt/control
Options are;
We have tested this with Linux Kernel 4.4.0
You can do this at runtime if you want to. I found a nice solution described here: http://www.absolutelytech.com/2011/08/01/how-to-disable-cpu-cores-in-linux/
Step 1: Identify the linux CPUs you want to switch off:
cat /proc/cpuinfo
Look for the CPUs that have the same "core id", you want to switch off one of each pair.
Step 2: Switch off the hyperthreading CPUs (in my case the last four of the total 8 "CPUs" seen by Linux)
echo 0 > /sys/devices/system/cpu/cpu4/online
echo 0 > /sys/devices/system/cpu/cpu5/online
echo 0 > /sys/devices/system/cpu/cpu6/online
echo 0 > /sys/devices/system/cpu/cpu7/online
You could setup yourself a script that you run just after system start.
To disable hyperthreading I include a script on machine /etc/rc.local. It is not exaclty clean, but is easy to install, independent of cpu architecture and should work on any modern linux distribution.
nano /etc/rc.local
# place this near the end before the "exit 0"
for CPU in /sys/devices/system/cpu/cpu[0-9]*; do
CPUID=$(basename $CPU)
echo "CPU: $CPUID";
if test -e $CPU/online; then
echo "1" > $CPU/online;
fi;
COREID="$(cat $CPU/topology/core_id)";
eval "COREENABLE=\"\${core${COREID}enable}\"";
if ${COREENABLE:-true}; then
echo "${CPU} core=${CORE} -> enable"
eval "core${COREID}enable='false'";
else
echo "$CPU core=${CORE} -> disable";
echo "0" > "$CPU/online";
fi;
done;
Linux kernel information and controls can be accessed as files in /sys directory on modern linux distributions. For example:
/sys/devices/system/cpu/cpu3 contains the kernel information and controls for logical cpu 3.
cat /sys/devices/system/cpu/cpu3/topology/core_id will show the core number this logical cpu belongs to.
echo "0" > /sys/devices/system/cpu/cpu3/online allows to disable logical cpu 3.
I do not know exactly why... but the system become more responsive with hyperthreading off (on my i5 notebook and massive Xeon servers with 60+ cores). I guess that has to do with per-cpu caches, per-cpu memory allocation, cpu scheduler allocation and process priorities complex iterations. I think the benefits of hyperthreading is outweight by the complexity of making cpu schedulers that know how to use it.
For me, the problem with hyperthreading is: If I start as many cpu-intensive threads as I have logical cores, I will have fast context switches for the cpu intensive tasks, but expensive ones for the background tasks since the hyperthreading totally consumed by the cpu intensive tasks. On the other hand, if I start as many cpu-intensive threads as I have physical cores I will have no context switches to those tasks and fast context switches for the background tasks. Seems good, but the background tasks will found free logical processors and will run almost imediatedly. It is like they are realtime performace (nice -20).
In the first scenario the hyperthreading is uselles, the background tasks will use expensive context switches because I maxed out hyperthreading with the normal processing. The second is unaceptable because up to 50% of my cpu power gets prioritized to the background tasks.
The "cpu-intensive" tasks I am talking about are artificial intelligence data mining and authorization servers (my work). Blender rendering in cheap computers and clusters (to sketch my future house).
Also, this is guesswork.
I have the impression that is better, but it may not.
You can use the "thread_siblings_list" for each core to turn off the second core in the HT pair.
The following command pipeline is hacky, not optimised, and done this way hopefully to make it easier to understand.
cat /sys/devices/system/cpu/cpu*/topology/thread_siblings_list | \
awk -F, '{print $2}' | \
sort -n | \
uniq | \
( while read X ; do echo $X ; echo 0 > /sys/devices/system/cpu/cpu$X/online ; done )
so, take all the thread siblings lists, extract the second CPU for each pair, get a unique list, and then turn them off.
does this make sense?
if I do "cat /proc/cpuinfo" after running the above, the number of cores halves.
For really old kernels (Linux 2.6.9 or so), append the noht parameter to the kernel on boot.
This kernel command-line option has been removed since at least Linux 2.6.18.
From http://www.faqs.org/docs/Linux-HOWTO/BootPrompt-HOWTO.html :
The `noht' Argument
This will disable hyper-threading on intel processors that have this feature.
If using lilo edit you /etc/lilo.conf (and run lilo afterwards) or if using grub then edit your /boot/grub/menu.lst .
Disable SMT / HT at boot time using the kernel command line parameter nosmt:
nosmt [KNL,S390] Disable symmetric multithreading (SMT).
Equivalent to smt=1.
[KNL,x86] Disable symmetric multithreading (SMT).
nosmt=force: Force disable SMT, cannot be undone
via the sysfs control file.
Disable SMT / HT at runtime using SMT control:
/sys/devices/system/cpu/smt/control:
This file allows to read out the SMT control state and provides the
ability to disable or (re)enable SMT. The possible states are:
============== ===================================================
on SMT is supported by the CPU and enabled. All
logical CPUs can be onlined and offlined without
restrictions.
off SMT is supported by the CPU and disabled. Only
the so called primary SMT threads can be onlined
and offlined without restrictions. An attempt to
online a non-primary sibling is rejected
forceoff Same as 'off' but the state cannot be controlled.
Attempts to write to the control file are rejected.
notsupported The processor does not support SMT. It's therefore
not affected by the SMT implications of L1TF.
Attempts to write to the control file are rejected.
============== ===================================================
The possible states which can be written into this file to control SMT
state are:
- on
- off
- forceoff
Lukas' answer is nice but does not really work for disabling HT because core ID cannot serve for identification of HT siblings. This script works instead:
#!/bin/bash
for CPU in /sys/devices/system/cpu/cpu[0-9]*; do
CPUID=`basename $CPU | cut -b4-`
echo -en "CPU: $CPUID\t"
[ -e $CPU/online ] && echo "1" > $CPU/online
THREAD1=`cat $CPU/topology/thread_siblings_list | cut -f1 -d,`
if [ $CPUID = $THREAD1 ]; then
echo "-> enable"
[ -e $CPU/online ] && echo "1" > $CPU/online
else
echo "-> disable"
echo "0" > $CPU/online
fi
done
I had to wait until I could get into the ILO/Drac. The kernel boot parameters do not work on current Linux distributions.
In the libsmbios-bin package (Debian, Ubuntu, etc), you have the binaries isCmosTokenActive and activateCmosToken. Together with the token list, you can then try something like this:
# isCmosTokenActive 0x00d1 # CPU_Hyperthreading_Enable
[...] Type 0x00d1 Location 0x46 AND(fe) OR(0) BITFIELD: 1
# isCmosTokenActive 0x00d2 # CPU_Hyperthreading_Disable
[....] Type 0x00d2 Location 0x46 AND(fe) OR(1) BITFIELD: 0
Then activate the CPU_Hyperthreading_Disable token:
# activateCmosToken 0x00d2 # CPU_Hyperthreading_Disable
[...] Type 0x00d2 Location 0x46 AND(fe) OR(1) BITFIELD: 1
Verify:
# isCmosTokenActive 0x00d1 # CPU_Hyperthreading_Enable
[...] Type 0x00d1 Location 0x46 AND(fe) OR(0) BITFIELD: 0
# isCmosTokenActive 0x00d2 # CPU_Hyperthreading_Disable
[...] Type 0x00d2 Location 0x46 AND(fe) OR(1) BITFIELD: 1
Now, the big question is whether or not you simply need a reboot for this to take effect, or if a full power cycle is required. Try it out and see how it goes!
Based on info provided by Paul M here, I'd "script" it this way:
fgrep , /sys/devices/system/cpu/cpu*/topology/thread_siblings_list |
cut -d, -f2 | sort -u |
sudo xargs -rI, sh -c 'echo 0 > /sys/devices/system/cpu/cpu,/online'
Of course it's not turning off hyper-threading in same sense as tinkering with BIOS would do, basically it only tells kernel task scheduler not to use some cores cause we know they're fake ones.
Software that made its assumption based on previous state of /proc or /sys sub-system still might be running sub-optimal or even fail due to this run-time change so its restart might be required. For e. g., I've noticed irqbalance was prone to fail in that circumstances.
Disable HT:
echo 0 |sudo tee /sys/devices/system/cpu/cpu{4..7}/online
Enable HT:
echo 1 |sudo tee /sys/devices/system/cpu/cpu{4..7}/online
Note: This do not really disable HyperThreading but they disable the "fake" cores obtaining almost the same result.
Old topic, but had reason to try this experiment. First, I am not at all certain that disabling the (slightly fake) CPUs at runtime is truly equivalent to disabling Hyperthreading at boot. That said, I did see a small performance boost in our application. (But not enough to keep.)
Used the thread_siblings value (common to hyperthreaded CPUs) as a key for enable/disable:
for i in /sys/devices/system/cpu/cpu[0-9]*
do echo "$(cat $i/topology/thread_siblings) $i"
done |
awk '{v = (a[$1] ? 0 : 1); a[$1] = 1; print "echo " v " > " $2 "/online"}' |
sudo sh
Try the command w/o the final sudo sh to verify correct.
