[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Factoring out standard system information
From:       Adriaan de Groot <groot () kde ! org>
Date:       2005-12-30 2:00:03
Message-ID: 200512300300.03968.groot () kde ! org
[Download RAW message or body]


There's a couple of non-portable system things that are really popular to know 
for KDE applications. These are CPU information (load; percentage time idle, 
interrupt, user, etc.), swap and RAM information (free and used). Reading 
these data is a pain in the ass, and it's implemented who knows how many 
times across the KDE codebase -- superkaramba, ksysguard and the just 
discovered (and hopelessly buggy) ktimemon come to mind. I think SK has the 
most accurate code - at least it gives me numbers that match what top(1) and 
swapinfo(8) tell me. KTimeMon has support for OSF but not for FreeBSD, which 
is .. uncomfortable and/or weird.

So would it make sense to factor this stuff out and stick it in kdelibs 
somewhere? ksysinfo or some such -- one central place to query system 
resource usage, so there's only one place reading /proc/icky/memusage or 
calling sysctlbyname("hw.memusage") or calling table() or using kvm(4).

How does that square with SK's merger into plasma? The system resource reading 
is some of the most popular stuff in SK.


-- 
These are your friends - Adem
    GPG: FEA2 A3FE Adriaan de Groot

[Attachment #3 (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]