Public bug reported:

We're seeing hundreds of kernel worker threads being spawned with some
actions, for example, after booting the desktop and hutting the
brightness keys causes this.  On investigation, this occurs when
CONFIG_SLAB is being used.

1. Ubuntu traditionally uses CONFIG_SLUB, so we should use that instead of 
CONFIG_SLAB (why was it changed for Yakkety?)
2. With CONFIG_SLUB I cannot reproduce the issue of the hundreds for worker 
threads
3 CONFIG_SLUB seems more performant on the boot too over SLAB.

Please re-enable the CONFIG_SLUB allocator as per the 4.4. Xenial
configs.

** Affects: linux (Ubuntu)
     Importance: High
         Status: New


** Tags: kernel-4.8

** Tags added: kernel-4.8

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1626564

Title:
  4.8 regression: SLAB is being used instead of SLUB

Status in linux package in Ubuntu:
  New

Bug description:
  We're seeing hundreds of kernel worker threads being spawned with some
  actions, for example, after booting the desktop and hutting the
  brightness keys causes this.  On investigation, this occurs when
  CONFIG_SLAB is being used.

  1. Ubuntu traditionally uses CONFIG_SLUB, so we should use that instead of 
CONFIG_SLAB (why was it changed for Yakkety?)
  2. With CONFIG_SLUB I cannot reproduce the issue of the hundreds for worker 
threads
  3 CONFIG_SLUB seems more performant on the boot too over SLAB.

  Please re-enable the CONFIG_SLUB allocator as per the 4.4. Xenial
  configs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626564/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to