kernel should have CONFIG_CFQ_GROUP_IOSCHED

Bug #706394 reported by poelzi
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Tim Gardner
Natty
Fix Released
Undecided
Tim Gardner

Bug Description

Please enable:
CONFIG_CFQ_GROUP_IOSCHED=y

This allows fair scheduling on IO with cgroups. ulatencyd uses this to make the system more responsible when a lot of io is happening. When cgroups is not used, this option will not cause any harm.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.37-12-generic 2.6.37-12.26
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.37-12.26-generic 2.6.37
Uname: Linux 2.6.37-12-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: I82801AAICH [Intel 82801AA-ICH], device 0: Intel ICH [Intel 82801AA-ICH]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: test 1172 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'I82801AAICH'/'Intel 82801AA-ICH with STAC9700,83,84 at irq 5'
   Mixer name : 'SigmaTel STAC9700,83,84'
   Components : 'AC97a:83847600'
   Controls : 34
   Simple ctrls : 24
Date: Sat Jan 22 21:03:14 2011
HibernationDevice: RESUME=UUID=c1f7baa2-afb0-4db8-b189-183db0e0fd54
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: innotek GmbH VirtualBox
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.37-12-generic root=UUID=4566f31c-3210-4345-b625-bdc377ae2dc2 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-2.6.37-12-generic N/A
 linux-backports-modules-2.6.37-12-generic N/A
 linux-firmware 1.45
RfKill:

SourcePackage: linux
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

Revision history for this message
poelzi (poelzi) wrote :
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi poelzi,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
poelzi (poelzi) wrote :

this patch adds the missing option required for blkio cgroups. it is usefull for all systems, so i put it in common.

Tim Gardner (timg-tpi)
Changed in linux (Ubuntu Natty):
assignee: nobody → Tim Gardner (timg-tpi)
status: Incomplete → Fix Committed
Revision history for this message
poelzi (poelzi) wrote :

I'm not so sure my patch fixed it. I tried using https://help.ubuntu.com/community/Kernel/Compile and other pages but can't find any good informations how all the scripts work together to build the kernel config. And how to make proper changes to all architectures.

a short test revealed that it seems not to be set correctly.

Revision history for this message
Tim Gardner (timg-tpi) wrote :

The kernel in pre-proposed has your config option enabled:

deb http://ppa.launchpad.net/kernel-ppa/pre-proposed/ubuntu natty main

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 2.6.38-3.30

---------------
linux (2.6.38-3.30) natty; urgency=low

  [ Andy Whitcroft ]

  * rebase to v2.6.38-rc4
  * ppc64 -- add basic architecture
  * ubuntu: AUFS -- update to 65835da20b77c98fb538c9114fc31f5de1328230

  [ Colin Ian King ]

  * SAUCE: Add WMI hotkeys support for Dell All-In-One series
    - LP: #676997
  * SAUCE: Add WMI hotkeys support for another Dell All-In-One series
    - LP: #701530
  * SAUCE: Dell WMI: Use sparse keymaps and tidy up code.
    - LP: #701530

  [ Dan Rosenberg ]

  * SAUCE: (drop after 2.6.38) Convert net %p usage %pK

  [ Kees Cook ]

  * Revert "SAUCE: kernel: make /proc/kallsyms mode 400 to reduce ease of
    attacking"
  * SAUCE: (drop after 2.6.38) use %pK for /proc/kallsyms and /proc/modules

  [ Tim Gardner ]

  * [Config] CONFIG_BLK_CGROUP=y
    - LP: #706394
  * [Config] CONFIG_DELL_WMI_AIO=m

  [ Upstream Kernel Changes ]

  * drm/i915/lvds: Restore dithering on native modes for gen2/3
    - LP: #711568

  [ Upstream Kernel Changes ]

  * rebase from v2.6.38-rc3 to v2.6.38-rc4.
 -- Andy Whitcroft <email address hidden> Tue, 08 Feb 2011 02:07:18 +0000

Changed in linux (Ubuntu Natty):
status: Fix Committed → Fix Released
Revision history for this message
Alan Lord (theopensourcerer) wrote :

Any chance this config patch (comment #3) could get backported to 10.04 LTS server?

It is currently not possible to use the blkio subsystem in cgroups which we'd like to do for managing some KVM guests. Our hosts are running 10.04LTS.

Revision history for this message
Tim Gardner (timg-tpi) wrote :

Alan - That feature didn't get implemented until 2.6.35. However, you can take advantage of it by running the Maverick LTS kernel (linux-image-server-lts-backport-maverick).

Revision history for this message
Alan Lord (theopensourcerer) wrote :

Thanks Tim, that's helpful.

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.