linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Cesar Eduardo Barros <cesarb@nitnet.com.br>
To: linux-kernel@vger.rutgers.edu
Cc: linux-mm@kvack.org
Subject: kswapd eating too much CPU on ac16/ac18
Date: Tue, 13 Jun 2000 20:51:58 -0300	[thread overview]
Message-ID: <20000613205158.A9782@cesarb.personal> (raw)

I've seen this behavior both in ac16 and in ac18. ac4 worked fine (and was the
fastest kernel I've ever seen on that box)

The box is a 386SX25, with 8MB RAM. The problem is that kswapd eats 99.0% of
the CPU while running dpkg (I also made it happen with X). dpkg uses 10MB of
memory in a particulary awful access pattern (so it swaps a lot).

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
by kswapd (running top -s and vmstat 1 at the same time). When the problem
happens everything seems to hang (vmstat lumps some seconds into one, as I can
see in the interrupt count), no disk activity happens (as if it was lost
thinking what to do next), and on the next update I can see kswapd ate an awful
amount of CPU (ok, top eats 20% CPU on that box, but why would ac4 remain
pretty responsive when ac16/ac18 stop to a halt?)

It's not zone related (only 8Mb of memory)

To reproduce: use mem=8M (or use a box like mine ;) ) and run dpkg --list (or
even better, try to install something using dpkg)

I think new VM ideas should always be tested with mem=8M and a dpkg run...

-- 
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/

             reply	other threads:[~2000-06-13 23:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-13 23:51 Cesar Eduardo Barros [this message]
2000-06-14  0:00 ` Alan Cox
2000-06-14  0:10   ` Cesar Eduardo Barros
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
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=20000613205158.A9782@cesarb.personal \
    --to=cesarb@nitnet.com.br \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox