I think that *-lowlatency-* kernels should include CONFIG_LATENCYTOP by
default. I agree that *-generic-* kernels do not need that. If
administrator has installed lowlatency kernel they clearly are
interested in lowest possible latency and Ubuntu should provide tools to
figure out where the current bottlenecks are.

Does popcon support querying for combination of lowlatency kernel AND
latencytop? Also note that since the CONFIG_LATENCYTOP was dropped,
latencytop is practically broken and cannot be used for anything, which
could explain its low usage.

(I also wonder if the increased RAM usage is *really* a big deal for
desktop class machines. Sure, CONFIG_LATENCYTOP may increase RAM usage
by 3848 bytes per task but for busy desktop or workstation running
around 1000 tasks that will result in increase of less than 4 *MB*. If
you're running 1000 tasks today, you probably have at least 4 *GB* of
RAM so the difference is less than 0.1%.)

-- 
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/1655986

Title:
  lowlatency kernel is lacking support for latencytop

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  Actual behavior:

  $ sudo latencytop
  mount: none is already mounted or /sys/kernel/debug busy
  Please enable the CONFIG_LATENCYTOP configuration in your kernel.
  Exiting...

  $ grep -i latencytop /boot/config-`uname -r`
  CONFIG_HAVE_LATENCYTOP_SUPPORT=y
  # CONFIG_LATENCYTOP is not set

  
  Expected behavior:

  # working latencytop and
  $ grep -i latencytop /boot/config-`uname -r`
  CONFIG_HAVE_LATENCYTOP_SUPPORT=y
  CONFIG_LATENCYTOP=y

  
  Tested with package linux-image-4.4.0-57-lowlatency.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-lowlatency 4.4.0.59.62
  ProcVersionSignature: Ubuntu 4.4.0-57.78-lowlatency 4.4.35
  Uname: Linux 4.4.0-57-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  mira       2801 F.... pulseaudio
  CurrentDesktop: MATE
  Date: Thu Jan 12 16:33:59 2017
  EcryptfsInUse: Yes
  HibernationDevice:
   #RESUME=UUID=609d4e01-862b-4199-bd45-ad8841f8c8c3
   #RESUME=UUID=69fefec2-0a4f-489b-bb6e-62eab3d97735
  InstallationDate: Installed on 2009-10-08 (2652 days ago)
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Alpha amd64 (20091008)
  IwConfig:
   lo        no wireless extensions.
   
   eth1      no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-lowlatency 
root=UUID=23b87e6c-20b4-4242-9489-1599d62abcce ro vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-57-lowlatency N/A
   linux-backports-modules-4.4.0-57-lowlatency  N/A
   linux-firmware                               1.157.6
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-11-14 (59 days ago)
  dmi.bios.date: 08/20/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1401
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H77-M PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1401:bd08/20/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655986/+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