From: Stephan von Krawczynski <skraw@ithnet.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: alan@lxorguk.ukuu.org.uk, akpm@zip.com.au, znmeb@aracnet.com,
art@lsr.nei.nih.gov, linux-kernel@vger.kernel.org
Subject: Re: kswapd etc hogging machine
Date: Thu, 3 Jan 2002 18:27:56 +0100 [thread overview]
Message-ID: <20020103182756.237453bd.skraw@ithnet.com> (raw)
In-Reply-To: <Pine.LNX.4.33L.0201031448410.24031-100000@imladris.surriel.com>
In-Reply-To: <E16M72b-0008B8-00@the-village.bc.nu> <Pine.LNX.4.33L.0201031448410.24031-100000@imladris.surriel.com>
On Thu, 3 Jan 2002 14:51:01 -0200 (BRST)
Rik van Riel <riel@conectiva.com.br> wrote:
> On Thu, 3 Jan 2002, Alan Cox wrote:
>
> > 2.4.1x VM code is performing better under light loads but its
> > absolutely and completely hopeless under a real paging load. 2.4.17-aa
> > is somewhat better interestingly.
>
> A quick 'make -j bzImage' test I did yesterday got the system
> to use near 70% of its CPU time in user mode and 30% in system
> mode. This was with 2.4.17-rmap-10b, btw.
And what kind of an argument is this? This is an honest question, really. If I
do this make I end up around 80-90% in user mode and the rest in system on a
standard 2.4.17 SMP box (configured with too less swap btw).
???
Regards,
Stephan
next prev parent reply other threads:[~2002-01-03 17:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-03 3:33 kswapd etc hogging machine Art Hays
2002-01-03 4:01 ` M. Edward Borasky
2002-01-03 4:13 ` Dave Jones
2002-01-03 5:15 ` Andrew Morton
2002-01-03 5:48 ` Daniel Phillips
2002-01-03 5:54 ` Jeffrey W. Baker
2002-01-03 12:32 ` Alan Cox
2002-01-03 16:51 ` Rik van Riel
2002-01-03 17:27 ` Stephan von Krawczynski [this message]
2002-01-03 17:32 ` Rik van Riel
2002-01-03 23:42 ` Stephan von Krawczynski
2002-01-03 18:59 ` Andrew Morton
2002-01-04 7:06 ` Art Hays
2002-01-03 12:37 ` Alan Cox
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=20020103182756.237453bd.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=akpm@zip.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=art@lsr.nei.nih.gov \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=znmeb@aracnet.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.