CONFIG_NO_HZ_IDLE should be the default

Bug #1413968 reported by Andy Whitcroft
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Medium
Andy Whitcroft

Bug Description

We have a hodge podge of CONFIG_NO_HZ_IDLE and CONFIG_NO_HZ_FULL selected across the architectures. From the documentation for CONFIG_NO_HZ_FULL this option does not even do anything positive until the user supplied a CPU list on the kernel command line, and it incurs a significant overhead overall. From the docs we should commonise on CONFIG_NO_HZ_IDLE, and separately evaluate the overhead.

Revision history for this message
Andy Whitcroft (apw) wrote :

Filed Bug #1413969 for the evaluation of the related options.

Changed in linux (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
assignee: nobody → Andy Whitcroft (apw)
milestone: none → ubuntu-15.01
Andy Whitcroft (apw)
Changed in linux (Ubuntu):
milestone: ubuntu-15.01 → ubuntu-15.02
Andy Whitcroft (apw)
Changed in linux (Ubuntu):
status: Confirmed → Fix Committed
Andy Whitcroft (apw)
Changed in linux (Ubuntu):
milestone: ubuntu-15.02 → ubuntu-15.03
Revision history for this message
Andy Whitcroft (apw) wrote :

Confirmed as applied and released as of Ubuntu-3.19.0-7.7.

Changed in linux (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.