2012-04-18 03:06:00 +02:00
|
|
|
config BR2_PACKAGE_LATENCYTOP
|
|
|
|
bool "latencytop"
|
2013-07-15 21:47:50 +02:00
|
|
|
depends on BR2_USE_WCHAR # libglib2
|
|
|
|
depends on BR2_TOOLCHAIN_HAS_THREADS # libglib2
|
2013-11-20 18:29:45 +01:00
|
|
|
depends on BR2_USE_MMU # libglib2
|
2012-04-18 03:06:00 +02:00
|
|
|
select BR2_PACKAGE_NCURSES
|
|
|
|
select BR2_PACKAGE_LIBGLIB2
|
|
|
|
help
|
|
|
|
There are many types and causes of latency. LatencyTOP
|
|
|
|
focuses on the type of latency that causes skips in audio,
|
|
|
|
stutters in your desktop experience or that overloads your
|
|
|
|
server (while you have plenty of CPU power left).
|
|
|
|
|
|
|
|
LatencyTOP focuses on the cases where the applications want
|
|
|
|
to run and execute useful code, but there's some resource
|
|
|
|
that's not currently available (and the kernel then blocks
|
|
|
|
the process). This is done both on a system level and on a
|
|
|
|
per process level, so that you can see what's happening to
|
|
|
|
the system, and which process is suffering and/or causing
|
|
|
|
the delays.
|
|
|
|
|
|
|
|
http://www.latencytop.org
|
|
|
|
|
2013-10-13 16:55:32 +02:00
|
|
|
comment "latencytop needs a toolchain w/ wchar, threads"
|
2013-11-20 18:29:45 +01:00
|
|
|
depends on BR2_USE_MMU
|
2013-07-15 21:47:50 +02:00
|
|
|
depends on !BR2_USE_WCHAR || !BR2_TOOLCHAIN_HAS_THREADS
|