From: Andrea Arcangeli <andrea@suse.de>
To: Rik van Riel <riel@redhat.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, robert_hentosh@dell.com
Subject: Re: [PATCH][2/2] do not OOM kill if we skip writing many pages
Date: Sun, 2 Jan 2005 18:29:29 +0100 [thread overview]
Message-ID: <20050102172929.GL5164@dualathlon.random> (raw)
In-Reply-To: <Pine.LNX.4.61.0412201013420.13935@chimarrao.boston.redhat.com>
On Mon, Dec 20, 2004 at 10:17:28AM -0500, Rik van Riel wrote:
> Simply running "dd if=/dev/zero of=/dev/hd<one you can miss>" will
> result in OOM kills, with the dirty pagecache completely filling up
> lowmem. This patch is part 2 to fixing that problem.
>
> Note that this test case demonstrates that the false OOM kills can
> also be reproduced with pages that are not "pinned" by the swap token
> at all, so there are some serious VM problems left still...
>
> If we cannot write out a number of pages because of congestion on
> the filesystem or block device, do not cause an OOM kill. These
> pages will become freeable later, when the congestion clears.
I don't like this one, it's much less obvious than 1/2. After your
obviously right 1/2 we're already guaranteed at least a percentage of
the ram will not be dirty. Is the below really needed even after 1/2 +
Andrew's fix? Are you sure this isn't a workaround for the lack of
Andrew's fix.
This 2/2 is absolutely generic, not related to highmem, and I'm at least
not having problem with Andrew's patch applied.
The conditional to out_of_memory especially looks not good, and I'm
scared it could generate livelocks.
I'm going to apply both your 1/2 and I already applied Andrew's
total_scanned, but from my part I'm not applying this 2/2. I believe to
be already safe with total_scanned + 1/2.
next prev parent reply other threads:[~2005-01-02 17:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-20 15:17 [PATCH][2/2] do not OOM kill if we skip writing many pages Rik van Riel
2005-01-02 17:29 ` Andrea Arcangeli [this message]
2005-01-03 4:20 ` Rik van Riel
2005-01-03 12:22 ` Marcelo Tosatti
2005-01-03 16:25 ` Andrea Arcangeli
2005-01-03 16:40 ` Rik van Riel
2005-01-03 17:10 ` Rik van Riel
2005-01-03 18:51 ` Marcelo Tosatti
2005-01-03 22:01 ` 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=20050102172929.GL5164@dualathlon.random \
--to=andrea@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
--cc=robert_hentosh@dell.com \
/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