From: Mark Lord <lkml@rtr.ca>
To: Con Kolivas <kernel@kolivas.org>
Cc: Serge Belyshev <belyshev@depni.sinp.msu.ru>,
William Lee Irwin III <wli@holomorphy.com>,
Matt Mackall <mpm@selenic.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
akpm@linux-foundation.org
Subject: Re: 2.6.21-rc3-mm1 RSDL results
Date: Tue, 13 Mar 2007 14:21:38 -0400 [thread overview]
Message-ID: <45F6EBB2.8090700@rtr.ca> (raw)
In-Reply-To: <200703111034.02159.kernel@kolivas.org>
Con Kolivas wrote:
>
> Can you try the new version of RSDL. Assuming it doesn't oops on you it has
> some accounting bugfixes which may have been biting you.
Retesting today with 2.6.21-rc3-git7 + 2.6.21-rc3-sched-rsdl-0.30.patch.
Still not pleasant to use the GUI with a kernel build (-j1 or -j2) happening
unless the build is manually "nice'd".
Also, accounting looks weird in top(1).
With a 100% busy machine, top will show something like this :
> top - 14:20:11 up 10:22, 1 user, load average: 2.65, 2.80, 2.18
> Tasks: 134 total, 4 running, 128 sleeping, 0 stopped, 2 zombie
> Cpu(s): 68.7% us, 6.7% sy, 24.7% ni, 0.0% id, 0.0% wa, 0.0% hi, 0.0% si
> Mem: 2076964k total, 2002560k used, 74404k free, 148924k buffers
> Swap: 2409740k total, 244k used, 2409496k free, 1448876k cached
>
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> 1824 root 36 10 11748 7244 1936 R 4.0 0.3 0:00.12 cc1
> 1845 root 31 0 8080 5272 1412 R 1.7 0.3 0:00.05 cc1
> 4139 root 20 0 176m 35m 6860 S 1.3 1.7 18:59.35 Xorg
> 29381 root 20 0 33712 16m 12m R 1.0 0.8 0:27.24 konsole
> 3 root 20 0 0 0 0 S 0.3 0.0 0:00.49 events/0
> 1529 root 20 0 2556 1460 752 S 0.3 0.1 0:00.05 make
> 14623 root 20 0 2200 1144 860 R 0.3 0.1 0:00.89 top
> 1 root 20 0 1568 532 464 S 0.0 0.0 0:00.22 init
> 2 root 39 19 0 0 0 S 0.0 0.0 0:00.01 ksoftirqd/0
> 4 root 20 0 0 0 0 S 0.0 0.0 0:00.00 khelper
> 5 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kthread
Mmm.. I wonder where all of that 100% CPU went to.. the busiest tasks
are only showing up as 4.0% and 1.7% (when in fact they are using near 100%).
Cheers
next prev parent reply other threads:[~2007-03-13 18:21 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-09 5:39 2.6.21-rc3-mm1 RSDL results Matt Mackall
2007-03-09 6:28 ` Con Kolivas
2007-03-09 7:53 ` Matt Mackall
2007-03-09 8:20 ` Matt Mackall
2007-03-09 8:39 ` Con Kolivas
2007-03-09 18:27 ` Matt Mackall
2007-03-09 20:15 ` Con Kolivas
2007-03-09 20:26 ` Con Kolivas
2007-03-09 20:51 ` Matt Mackall
2007-03-09 20:55 ` Matt Mackall
2007-03-09 20:46 ` Matt Mackall
2007-03-09 21:07 ` Con Kolivas
2007-03-09 21:19 ` Con Kolivas
2007-03-09 21:39 ` Matt Mackall
2007-03-09 21:57 ` Con Kolivas
2007-03-09 22:18 ` Con Kolivas
2007-03-09 22:29 ` Matt Mackall
2007-03-09 23:02 ` Con Kolivas
2007-03-09 23:06 ` Matt Mackall
2007-03-10 0:31 ` Con Kolivas
2007-03-10 0:34 ` Con Kolivas
2007-03-10 0:49 ` Matt Mackall
2007-03-10 1:28 ` Con Kolivas
2007-03-10 1:42 ` Matt Mackall
2007-03-10 2:10 ` Kyle Moffett
2007-03-10 2:20 ` Con Kolivas
2007-03-10 2:26 ` Matt Mackall
2007-03-10 2:53 ` Con Kolivas
2007-03-09 21:57 ` Willy Tarreau
2007-03-09 22:12 ` Con Kolivas
2007-03-09 22:20 ` Matt Mackall
2007-03-09 22:31 ` Willy Tarreau
2007-03-10 1:02 ` Con Kolivas
2007-03-10 1:10 ` Matt Mackall
2007-03-10 17:01 ` James Cloos
2007-03-10 23:16 ` Con Kolivas
2007-03-11 12:38 ` James Cloos
2007-03-11 12:52 ` Con Kolivas
2007-03-09 21:10 ` Matt Mackall
2007-03-09 8:36 ` Con Kolivas
2007-03-09 9:07 ` Serge Belyshev
2007-03-09 9:49 ` William Lee Irwin III
2007-03-09 10:36 ` Serge Belyshev
2007-03-09 18:07 ` Mark Lord
2007-03-09 18:24 ` Jeffrey Hundstad
2007-03-09 20:23 ` Con Kolivas
2007-03-10 18:21 ` Mark Lord
2007-03-10 23:34 ` Con Kolivas
2007-03-10 23:38 ` Con Kolivas
2007-03-13 18:21 ` Mark Lord [this message]
2007-03-13 20:26 ` Con Kolivas
2007-03-13 22:06 ` Mark Lord
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45F6EBB2.8090700@rtr.ca \
--to=lkml@rtr.ca \
--cc=akpm@linux-foundation.org \
--cc=belyshev@depni.sinp.msu.ru \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=wli@holomorphy.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.