From: Ed Tomlinson <tomlins@cam.org>
To: David Ford <david@linux.com>
Cc: linux-kernel@vger.kernel.org
Subject: VM breakdown, 2.4.0 family
Date: Sat, 27 Jan 2001 09:59:32 -0500 [thread overview]
Message-ID: <01012709593200.27226@oscar> (raw)
David Ford Wrote:
>Since the testN series and up through ac12, I experience total loss of
>control when memory is nearly exhausted.
>
>I start with 256M and eat it up with programs until there is only about
>7 megs left, no swap. From that point all user processes stall and the
>disk begins to grind nonstop. It will continue to grind for about 25-30
>minutes until it goes completely silent. No processes get killed, no VM
>messages are emitted.
>
>The only recourse is the magic key. If I reboot before the disk goes
>silent I can cleanly kill X with sysrq-E and restart.
>
>If I wait until it goes silent, all is lost. I have to sysrq-SUB.
You might want to try:
http://bazar.conectiva.com.br/~marcelo/patches/v2.4/2.4.1pre10/bg_page_aging.patch
or
ftp://ftp.cam.org/users/tomlins/pte_aging_limit_swaps.diff
The first patch from Marcelo fixes a problem with aging the wrong pages. The
second patch is sort of a 'best of Marcelo' patch. It contains the aging fix
and adds conditional bg pte aging (if with activate fast than we age
down...). It also has code to trottle swapouts when under preasure - it only
swaps out as much as we need now.
I have fives days of uptime with it here (on test9 and test10).
Feedback Welcome,
Ed Tomlinson <tomlins@cam.org>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-01-27 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-27 14:59 Ed Tomlinson [this message]
2001-01-27 23:21 ` VM breakdown, 2.4.0 family David Ford
2001-01-27 23:04 ` Marcelo Tosatti
-- strict thread matches above, loose matches on Subject: below --
2001-01-27 7:38 David Ford
2001-01-27 22:41 ` Marcelo Tosatti
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=01012709593200.27226@oscar \
--to=tomlins@cam.org \
--cc=david@linux.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