From: Cesar Eduardo Barros <cesarb@nitnet.com.br>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Cesar Eduardo Barros <cesarb@nitnet.com.br>,
linux-kernel@vger.rutgers.edu, linux-mm@kvack.org
Subject: Re: kswapd eating too much CPU on ac16/ac18
Date: Tue, 13 Jun 2000 21:10:52 -0300 [thread overview]
Message-ID: <20000613211052.A9898@cesarb.personal> (raw)
In-Reply-To: <E1320bL-0008Af-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Wed, Jun 14, 2000 at 01:00:09AM +0100
On Wed, Jun 14, 2000 at 01:00:09AM +0100, Alan Cox wrote:
> > ac4 was faster than ever, it looked like it wasn't swapping at all
> >
> > ac16 and ac18 are both awful, dpkg takes an infinite time, all of it dominated
>
> Im interested to know if ac9/ac10 is the slow->fast change point
>
I didn't compile that... I jumped from ac4 to ac16. Maybe I'll compile it
tomorrow. Maybe later (exams).
--
Cesar Eduardo Barros
cesarb@nitnet.com.br
cesarb@dcc.ufrj.br
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-06-14 0:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-13 23:51 kswapd eating too much CPU on ac16/ac18 Cesar Eduardo Barros
2000-06-14 0:00 ` Alan Cox
2000-06-14 0:10 ` Cesar Eduardo Barros [this message]
2000-06-16 5:45 ` Mike Galbraith
2000-06-16 15:08 ` Rik van Riel
2000-06-17 3:05 ` Cesar Eduardo Barros
2000-06-17 4:04 ` Mike Galbraith
2000-06-17 14:06 ` Cesar Eduardo Barros
2000-06-17 15:25 ` Mike Galbraith
2000-06-17 15:23 ` Rik van Riel
2000-06-17 15:33 ` Rik van Riel
2000-06-19 21:22 ` Goswin Brederlow
2000-06-18 6:26 ` Mike Galbraith
-- strict thread matches above, loose matches on Subject: below --
2000-06-16 9:56 Roger Larsson
2000-06-17 19:43 Cesar Eduardo Barros
2000-06-17 21:34 ` Roger Larsson
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=20000613211052.A9898@cesarb.personal \
--to=cesarb@nitnet.com.br \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
/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.