LIKWID-SETFREQUENCIES(1)

πŸ’… LIKWID-SETFREQUENCIES πŸ’…

ok so bestie, welcome to likwid-setFrequencies, a little legend from the likwid-5 era (we're talking manual-page canon here, and the whole toolkit lives in likwid). It's a General Commands Manual entry, and no cap, it's literally the tool that lets you boss around your hardware threads' clock speed. Let's get into it 🫢


✨ NAME ✨

likwid-setFrequencies β€” print and manage the clock frequency of hardware threads. it's giving frequency whisperer πŸ‘‘


🌸 SYNOPSIS 🌸

likwid-setFrequencies [-hvplmp] [-c <cpu_list>] [-g <governor>]
[-f,--freq <frequency>] [-x,--min <min_freq>] [-y,--max <max_freq>]
[-t,--turbo <0|1>] [--umin <uncore_min_freq>] [--umax <uncore_max_freq>]
[--reset] [--ureset]

πŸ¦‹ DESCRIPTION πŸ¦‹

So likwid-setFrequencies is a command line application, and its whole main character job is setting the clock frequency of hardware threads. Obsessed.

But here's the thing, bestie: only priviledged users get to change the frequency of hardware threads. Which means this app doesn't solo it β€” it works in combination with a daemon, likwid-setFreq(1). That daemon needs the suid permission bit set, because otherwise it can't touch the sysfs entries. iykyk πŸ’€

With likwid-setFrequencies you can set the clock of all hardware threads inside the cpu_list or affinity domain to a specific frequency or governor, all at once. One command, many threads, immaculate efficiency.

And fr fr, it works now with the cpufreq drivers 'acpi-cpufreq' and 'intel_pstate'. 🌈


πŸ’– OPTIONS πŸ’–

  • -h β€” prints a help message to standard output, then exits. the classic "help me bestie" move πŸ’…
  • -p β€” prints the current frequencies for all hardware threads. vibe check on your clock speeds ✨
  • -l β€” prints all configurable frequencies. look at all the options, gorgeous
  • -m β€” prints all configurable governors. all of them, the full lineup πŸŽ€
  • -c <cpu_list> β€” set the affinity domain where to set the frequencies. Common ones are N (Node), SX (Socket X), CX (Cache Group X) and MX (Memory Group X). For detailed information about affinity domains see likwid-pin(1). yep, go read that one too πŸ“š
  • -g <governor> β€” set the governor of all hardware threads inside the affinity domain. Current governors are ondemand, performance, turbo. Default is ondemand. the default is giving "whatever, we'll figure it out" πŸ™ˆ
  • -f, --freq <frequency> β€” set a fixed frequency at all hardware threads inside the affinity domain. ⚠️ Heads up: it implicitly sets 'userspace' governor for the hardware threads when you're using the acpi-cpufreq driver. sneaky but iconic
  • -x, --min <min_freq> β€” set a fixed minimal frequency at all hardware threads inside the affinity domain. Can be used in combination with a dynamic governor. teamwork makes the dream work 🫢
  • -y, --max <max_freq> β€” set a fixed maximal frequency at all hardware threads inside the affinity domain. Can be used in combination with a dynamic governor. the ceiling, the limit, the budget πŸ“ˆ
  • -t, --turbo <0|1> β€” deactivates/activates Turbo mode for the specified hardware threads. 0 for chill, 1 for send it πŸ”₯
  • --umin <uncore_min_freq> β€” set the minimal frequency for the Uncore. There are no limits available, but likwid-setFrequencies allows the available minimal CPU frequency as minimal Uncore frequency. ⚠️ Only available for Intel architectures.
  • --umax <uncore_max_freq> β€” set the maximal frequency for the Uncore. There are no limits available, but likwid-setFrequencies allows the available maximal CPU frequency (with a single hardware thread and Turbo) as maximal Uncore frequency. ⚠️ Only available for Intel architectures.
  • --reset β€” resets the hardware threads to maximal range, deactivates Turbo mode, and sets the governor to "performance", "conservative" or the last one in the governor list as fallback. the "actually let's just start over" button 🧚
  • --ureset β€” resets the Uncore to maximal range. It uses the minimally available CPU frequency as minimal Uncore frequency and the maximally achievable CPU frequency (single core, Turbo active) as maximal Uncore frequency. clean slate, Uncore edition ⭐
not me pointing out that the synopsis shows -v in [-hvplmp] but the option list has no -v entry. I'm just saying what I see, bestie. πŸ’€

πŸ‘‘ AUTHOR πŸ‘‘

Written by Thomas Gruber <thomas.roehl@googlemail.com>. absolute legend, thank you for your service πŸ«‘πŸ’œ


πŸ“ BUGS πŸ“

Report Bugs on <https://github.com/RRZE-HPC/likwid/issues>. found a lil glitch? tell the devs, don't suffer in silence πŸ™ˆ


⭐ SEE ALSO ⭐

likwid-pin(1), likwid-perfctr(1), likwid-powermeter(1)


so yeah, that's the whole page, no details skipped, all facts intact, and that's on periodt πŸ’…βœ¨

this beauty is brought to you by likwid-5, dated 23.12.2025 β€” from the LIKWID-SETFREQUENCIES(1) page itself. go set some frequencies, bestie, you got this πŸ’–πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from