Package: latencytop Version: 0.3-4 Severity: normal Hi,
If I start two instances of latencytop and then quit one of them, the
other latencytop no longer displays any other latencies than for
waiting for the CPU. I believe this is caused by latencytop writing 0
to /proc/sys/kernel/latencytop at exit, therefore disabling the
collection of the information for the other process.
Another problem with this approach is if the latencytop process dies
for some reason without writing 0 to that file, in which case the
statistics collection is not disabled and (I believe) substantially
slows down the system.
I wonder if the proper solution would be some kind of kernel interface
where processes get latencytop information by reading from a file
under /proc, and the feature is disabled when no processes hold the
file open.
Sami
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.25-rc8 (SMP w/4 CPU cores)
Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash
Versions of packages latencytop depends on:
ii libc6 2.7-10 GNU C Library: Shared libraries
ii libglib2.0-0 2.16.3-2 The GLib library of C routines
ii libncursesw5 5.6+20080405-1 Shared libraries for terminal hand
latencytop recommends no packages.
-- no debconf information
signature.asc
Description: Digital signature
