Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Core parking is a new feature that introduced in Windows 7 to get better Battery performance .

Depending on the resource use of the operating system it may park one or multiple cores of a multi-core cpu to reduce the computer’s power consumption and thermal emissions. Once operations require more processing power, the parked cores are activated again to assist in the tasks

So my question is that is there any way i can do it on Ubuntu 12.04 " Core Parking " ?

share|improve this question
Great Question! – NlightNFotis Sep 9 '12 at 15:23
up vote 8 down vote accepted

For the time being, I do not have a clear answer for this, however it is obvious that the linux Kernel is using some energy saving mechanisms.

However, doing some quick research around, I quickly realised that the most recent Linux kernels make use of a feature called ACPI which is an acronym for Advanced Configuration and Power Interface.

What the ACPI is doing:

the Advanced Configuration and Power Interface (ACPI) specification provides an open standard for device configuration and power management by the operating system.

via Wikipedia.

Basically the ACPI allows for control of different CPU states, to allow for better power management.

Different ACPI CPU-states:

CPU C-States (power management)

Basically, there is probably nothing that you have to worry about concerning the CPU "C states". These are automatically controlled by the kernel+ACPI system taking into consideration current system load. (CAVEAT: check out the note about AMD Athlon and Duron processors below). The ACPI code in the newer (2.6+) kernels automatically puts your CPU to sleep when there is idle time (note: this does not change the CPU frequency. That is controlled by "P states" - see below).

The only thing to realize is that your system is completely "conscious" when the CPU is momentarily halted - you won't notice much of a difference. However, the power savings can be considerable. Just think of it as having your CPU taking thousands of "micro-naps" whenever it is idle.

CPU-T States (throttling)

These are very much like "C states" (the same HLT instruction is used), however the difference is that throttling is "forced by you" (like every 4th cycle is forced to be a sleep cycle, as opposed to the "C states" above which are automatically determined by the system load). Note that the frequency has NOT been changed... see the "P states" below.

CPU-P States (performance)

Many processors these days (especially laptops) can have the clock frequency actually slowed "on the fly". This adds up to huge power savings. Intel calls this "SpeedStep" and AMD calls it "Cool'n'Quiet" or "PowerNow". More generically these states are called "P states". You will almost certainly have to go into the BIOS and enable this feature for your CPU FIRST!

** Some consumption benchmarks:**

What are the power savings from the above CPU states? The following data is extracted from the AMD website. Consider an AMD 64 3400+/2200MHz with 1 MB of L2 cache. By the way, while I'm here, let me complain about the AMD naming convention. The number 3400+ doesn't mean jack squat. This is just AMD's way of saying that this processor "looks like" an Intel Pentium-4 running at 3400MHz. I guess this is their way of not losing marketshare. Here are the P and T state power consumption values (the C state is the same HLT instruction as the T state):

  • Performance State 0 (Fully Active) (2200MHz): 89 Watts
  • Performance State 1 (2000MHz): 70 Watts
  • Performance State 2 (800MHz): 35 Watts
  • Throttled (HLT instruction): 2.2 Watts

Some references for further reading


[EDIT #1]: Googling around, I found some other posts in some forums too (OpenSuse forum seems to be relevant to what you seek) and found out that this is not that much of an issue for Linux as it is for windows and especially in gaming. I also dug up some information in two mails (first one and second one [follow-up]) in the RedHat mailing lists that seems to be related. I am currently researching the information in it.

[EDIT #2]: I have researched the issue a bit, and I am getting more and more certain that there is not a core parking mechanism in Linux, unless there is one the ACPI that I am unaware of. Some interesting findings are some pieces of software that allow for direct manipulation of the cpu and the processes run on it, like cpuset, numactl and last but not least, CPUfreq. Will continue with my research.

share|improve this answer
I think some Android devices can disable one or more cores. Not sure if this is managed directly by the hardware or the kernel though. – Leo Sep 9 '12 at 19:19

There's an article here mentioning that core parking relates to setting cores to advance c-states to save power. c-states are set with the halt instruction. As NlightNFotis mentions this is done using linux's support for ACPI.

You may be able to get some more information about the states into which your cores are put by linux with the powertopInstall powertop open source program written by Intel. If your hardware supports various c-states it should be able to tell you what percentage of time your cores are put into these reduced-power states by Ubuntu Linux. See below. The higher number the c-state the more power that is saved.

It provides much more information as well.

Also, like Windows, when there is work to do Linux can adjust the frequency at which the cores run depending upon the amount of demand, desire to save power, etc.

My laptop doesn't support c-states, though it can be suspended. A little Acer we have with an Atom processor does support them, as you can see below.

enter image description here

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.