summaryrefslogtreecommitdiff
path: root/hurd/translator/procfs/jkoenig
diff options
context:
space:
mode:
Diffstat (limited to 'hurd/translator/procfs/jkoenig')
-rw-r--r--hurd/translator/procfs/jkoenig/discussion.mdwn23
1 files changed, 23 insertions, 0 deletions
diff --git a/hurd/translator/procfs/jkoenig/discussion.mdwn b/hurd/translator/procfs/jkoenig/discussion.mdwn
index e71ea02b..4cd4e5ca 100644
--- a/hurd/translator/procfs/jkoenig/discussion.mdwn
+++ b/hurd/translator/procfs/jkoenig/discussion.mdwn
@@ -337,3 +337,26 @@ filing these:
https://enc.com.au/2012/09/careful-with-pids/'
<pinotree> ?
<youpi> nope
+
+
+# CPU Usage
+
+## IRC, freenode, #hurd, 2013-01-30
+
+ <gnu_srs> Hi, htop seems to report CPU usage correct, but not top, is that
+ a known issue?
+ <youpi> does your /proc have the -c flag?
+ <gnu_srs> /hurd/procfs -c
+ <youpi> I don't remember which way it works, but iirc depending on whether
+ -c is there or not, it will work or not
+ <youpi> problem being that nothing says linux' clock is 100Hz, but a lot of
+ programs assume it
+ <gnu_srs> seems like htop gets it right though
+ <youpi> possibly just by luc
+ <youpi> k
+
+
+### IRC, freenode, #hurd, 2013-01-31
+
+ <braunr> both htop and top seem to have problems report the cpu time
+ <braunr> so i expect the problem to be in procfs