From: Rik van Riel <riel@redhat.com>
To: Linux kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kernel 2.6.22: what IS the VM doing?
Date: Tue, 04 Sep 2007 21:37:35 -0400 [thread overview]
Message-ID: <46DE085F.2040306@redhat.com> (raw)
In-Reply-To: <20070830115429.w2puzet5sllhccdk@m.safari.iki.fi>
Sami Farin wrote:
> Using SMP kernel 2.6.22.6pre-CFS-v20.5 on Pentium D (IA-32).
> I think this bug (or whatever you want to call it) got triggered
> when you first allocate several megabytes of memory in a kernel module
> and then free them, and then run e.g. X and when memory gets tight,
> you end up with this situation...
>
> Top 2 /proc/vmstat Biggest Winners:
>
> pgrefill_normal:49900/second
> pgrefill_high:20810/second
That means the pageout code was scanning about 70000 pages
per second on your system during peak stress. You may have
run into a scalability problem in the Linux kernel, where it
wants to clear the referenced bit off all the anonymous pages
before swapping something out.
To make matters worse, that unlucky page gets chosen because
it was the page where kswapd started scanning. It has little
to do with being the least recently used page, because every
anonymous page tends to have its referenced bit set by the time
we start scanning.
On truly enormous systems, say with 256GB of memory, kswapd
sometimes needs to scan hundreds of thousands or even millions
of pages before finding something to swap out. Not fun.
> Did I forget to include some info???
> Oh, and I need to reboot in order to get usable system
> when this bug happens.
Is the system trying to evict pages like crazy when your
system becomes unusable?
If so, I wonder if kswapd is simply doing the wrong thing
and trying to evict data from all zones, simply because the
highmem zone is low on free pages...
--
Politics is the struggle between those who want to make their country
the best in the world, and those who believe it already is. Each group
calls the other unpatriotic.
next prev parent reply other threads:[~2007-09-05 1:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 11:54 kernel 2.6.22: what IS the VM doing? Sami Farin
2007-09-05 1:37 ` Rik van Riel [this message]
2007-09-05 11:45 ` Sami Farin
2007-09-05 16:24 ` Rik van Riel
2007-09-05 17:33 ` Sami Farin
2007-09-05 22:48 ` Rik van Riel
2007-09-14 17:17 ` Sami Farin
2007-11-02 14:36 ` kernel 2.6.23: " Sami Farin
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=46DE085F.2040306@redhat.com \
--to=riel@redhat.com \
--cc=linux-kernel@vger.kernel.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