From: Szabolcs Szakacsits <szaka@f-secure.com>
To: Richard Jerrell <jerrell@missioncriticallinux.com>
Cc: linux-mm@kvack.org
Subject: Re: [PATCH] Reclaim orphaned swap pages
Date: Mon, 2 Apr 2001 20:17:50 +0200 (MET DST) [thread overview]
Message-ID: <Pine.LNX.4.30.0104021952000.406-100000@fs131-224.f-secure.com> (raw)
> From what I can see of the patch vm_enough_memory will still fail
> causing premature oom
Actually if vm_enough_memory fails that prevents oom, apps get ENOMEM
instead of killed by oom_kill later. Moreover vm_enough_memory is long
different and apparently it's just overestimating free pages that makes
people unhappy with the resulted higher oom_kill/ENOMEM rate. If you
want to prevent premature oom you should patch out_of_memory but be
careful if you overestimate you can/will lockup. Anyway I think the
right place for oom_kill would be in the page fault handler [just as for
early kernels] but this needs a small change in __alloc_pages otherwise
processes get stuck there [see goto try_again] when system is low on
memory.
Szaka
--
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/
next reply other threads:[~2001-04-02 18:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-02 18:17 Szabolcs Szakacsits [this message]
2001-04-02 18:40 ` Richard Jerrell
2001-04-02 18:40 ` Szabolcs Szakacsits
2001-04-03 0:19 ` Marcelo Tosatti
2001-04-03 13:27 ` Richard Jerrell
2001-04-03 22:11 ` Marcelo Tosatti
2001-04-04 14:29 ` Richard Jerrell
-- strict thread matches above, loose matches on Subject: below --
2001-04-02 15:17 Richard Jerrell
2001-03-31 22:46 Bulent Abali
2001-03-28 22:59 Stephen Tweedie
2001-03-30 19:59 ` Patrick O'Rourke
2001-03-30 22:16 ` Rik van Riel
2001-04-04 21:59 ` Stephen Tweedie
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=Pine.LNX.4.30.0104021952000.406-100000@fs131-224.f-secure.com \
--to=szaka@f-secure.com \
--cc=jerrell@missioncriticallinux.com \
--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