From: ebiederm@xmission.com (Eric W. Biederman)
To: Derek Glidden <dglidden@illusionary.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Break 2.4 VM in five easy steps
Date: 06 Jun 2001 12:52:07 -0600 [thread overview]
Message-ID: <m1ofs15tm0.fsf@frodo.biederman.org> (raw)
In-Reply-To: <3B1E7ABA.EECCBFE0@illusionary.com>
Derek Glidden <dglidden@illusionary.com> writes:
> The problem I reported is not that 2.4 uses huge amounts of swap but
> that trying to recover that swap off of disk under 2.4 can leave the
> machine in an entirely unresponsive state, while 2.2 handles identical
> situations gracefully.
>
The interesting thing from other reports is that it appears to be kswapd
using up CPU resources. Not the swapout code at all. So it appears
to be a fundamental VM issue. And calling swapoff is just a good way
to trigger it.
If you could confirm this by calling swapoff sometime other than at
reboot time. That might help. Say by running top on the console.
Eric
--
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-mm.org/
next parent reply other threads:[~2001-06-06 18:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3B1E4CD0.D16F58A8@illusionary.com>
[not found] ` <3b204fe5.4014698@mail.mbay.net>
[not found] ` <3B1E5316.F4B10172@illusionary.com>
[not found] ` <m1wv6p5uqp.fsf@frodo.biederman.org>
[not found] ` <3B1E7ABA.EECCBFE0@illusionary.com>
2001-06-06 18:52 ` Eric W. Biederman [this message]
2001-06-06 19:06 ` Mike Galbraith
2001-06-06 19:28 ` Eric W. Biederman
2001-06-07 4:32 ` Mike Galbraith
2001-06-07 6:38 ` Eric W. Biederman
2001-06-07 7:28 ` Mike Galbraith
2001-06-07 7:59 ` Eric W. Biederman
2001-06-07 8:15 ` Mike Galbraith
2001-06-07 17:10 ` Marcelo Tosatti
2001-06-07 17:43 ` Please test: workaround to help swapoff behaviour Marcelo Tosatti
2001-06-06 19:28 ` Break 2.4 VM in five easy steps Derek Glidden
2001-06-09 7:55 ` Rik van Riel
2001-06-07 14:22 Bulent Abali
2001-06-07 15:38 ` Mike Galbraith
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=m1ofs15tm0.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=dglidden@illusionary.com \
--cc=linux-kernel@vger.kernel.org \
--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