From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Mikhail Ramendik <mr@ramendik.ru>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.10-rc3: kswapd eats CPU on start of memory-eating task
Date: Tue, 14 Dec 2004 11:51:44 +1100 [thread overview]
Message-ID: <41BE3920.5020904@yahoo.com.au> (raw)
In-Reply-To: <200412121728.16968.mr@ramendik.ru>
Mikhail Ramendik wrote:
> Hello,
>
> With kernel 2.6.10-rc3 and 256 M RAM, when I start a task taht eats a ot of
> RAM (for example, viewing a big TIFF file; also tested with a synthetic
> "eater"), in the resulting swapping process kswapd tahes quite a bit of CPU
> time. The computer becomes extremely unresponsive, the clock (in icewm) stops
> for periods of time up to a minute). And the task startup itself is somewhaat
> slow.
>
> I have checked both 2.6.8.1 and 2.6.9 for comparison, and they fare a lot
> better. The CPU hogging is not there, the computer is much more responsive,
> and the task starts faster.
>
Hi Mikhail,
I'm not quite sure what the problem would be. Please check that you are using
the same config for each kernel, and both kernels have detected the same amount
of memory.
Then, can you start by posting /proc/vmstat before and after running the
synthetic "eater" for some amount of time, with both 2.6.9 and 2.6.10-rc3; so:
boot 2.6.9
cat /proc/vmstat > 2.6.9-pre ; ./eater ; cat /proc/vmstat 2.6.9-post
and the same for 2.6.10-rc3.
Also, /proc/meminfo and /proc/slabinfo output for each kernel before running
eater may give some clues.
Oh, and can you post the source code for the "eater" as well, please?
Thanks,
Nick
next prev parent reply other threads:[~2004-12-14 0:52 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-12 14:28 2.6.10-rc3: kswapd eats CPU on start of memory-eating task Mikhail Ramendik
2004-12-14 0:51 ` Nick Piggin [this message]
2004-12-14 2:28 ` Mikhail Ramendik
-- strict thread matches above, loose matches on Subject: below --
2004-12-14 7:24 Voluspa
2004-12-15 14:02 Voluspa
2004-12-17 0:41 ` Andrew Morton
2004-12-15 22:49 Voluspa
2004-12-16 8:03 ` Nick Piggin
2004-12-16 8:14 ` Nick Piggin
2004-12-17 10:45 Voluspa
2004-12-18 23:02 ` Con Kolivas
2004-12-19 14:08 Voluspa
2004-12-19 22:40 Voluspa
2004-12-19 22:56 ` Nick Piggin
2004-12-19 23:08 ` Mikhail Ramendik
2004-12-19 23:57 ` Andrew Morton
2004-12-20 0:03 ` Mikhail Ramendik
2004-12-20 3:02 ` Con Kolivas
2004-12-20 3:21 ` Rik van Riel
2004-12-20 4:13 ` Con Kolivas
2004-12-20 4:18 ` Rik van Riel
2004-12-20 4:21 ` Con Kolivas
2004-12-20 4:33 ` Nick Piggin
2004-12-20 7:07 ` Andrew Morton
2004-12-19 23:12 Voluspa
2004-12-20 6:51 Voluspa
2004-12-20 7:12 ` Andrew Morton
2004-12-20 7:44 ` Nick Piggin
2004-12-20 8:03 ` Con Kolivas
2004-12-20 8:58 ` Con Kolivas
2004-12-20 12:55 ` Andrea Arcangeli
2004-12-20 12:06 ` Ed Tomlinson
2004-12-20 12:29 ` Con Kolivas
2004-12-20 17:49 ` Hideo AOKI
2004-12-20 23:51 ` Nick Piggin
2004-12-20 9:07 ` mr
2004-12-20 15:06 ` Rik van Riel
2004-12-20 9:22 Zou, Nanhai
2004-12-20 15:08 ` Rik van Riel
2004-12-20 12:59 Voluspa
2004-12-21 1:46 ` Mikhail Ramendik
2004-12-22 8:45 Zou, Nanhai
2004-12-22 14:23 ` Rik van Riel
2004-12-23 0:26 Zou, Nanhai
2004-12-23 13:26 ` Rik van Riel
2004-12-23 13:28 ` Rik van Riel
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=41BE3920.5020904@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mr@ramendik.ru \
/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