From: Sami Farin <7atbggg02@sneakemail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][1/2] adjust dirty threshold for lowmem-only mappings
Date: Mon, 20 Dec 2004 19:56:35 +0200 [thread overview]
Message-ID: <20041220175635.GC7459@m.safari.iki.fi> (raw)
In-Reply-To: <037BE7456155544096945D871C4709AA01A99EB3@ausx2kmps318.aus.amer.dell.com>
On Mon, Dec 20, 2004 at 10:46:48AM -0600, Robert_Hentosh@Dell.com wrote:
>
>
> > On Mon, 20 Dec 2004, 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 1 to
> >> fixing that problem.
> >
> > What I forgot to say is that in order to trigger this OOM
> > Kill the dirty_limit of 40% needs to be more memory than
> > what fits in low memory. So this will work on x86 with
> > 4GB RAM, since the dirty_limit is 1.6GB, but the block
> > device cache cannot grow that big because it is restricted
> > to low memory.
> >
> > This has the effect of all low memory being tied up in
> > Dirty page cache and userspace try_to_free_pages() skipping
> > the writeout of these pages because the block device is
> > congested.
>
> I am just confirming that this is a real problem. The problem
> more frequently shows up with block sizes above 4k on the
> dd and also showed up on some platforms with just a mke2fs
> on a slower device such as a USB hard drive.
>
> Rik's patch has solved the issue and has been running under
> stress (via ctcs) over the weekend without failure.
Rik's patch was broken (word-wrap by pine), but I patched
manually. However, I have tglx-oom-final patch which moved
out_of_memory call from vmscan.c:try_to_free_pages()
to page_alloc.c:__alloc_pages().
Basically, (sc.nr_congested < SWAP_CLUSTER_MAX) check is missing.
So, what's the best way to combine these two patches?
If you use mutt, the patch can be found with command
/~i 1102697553.3306.91.camel@tglx.tec.linutronix.de
from your LKML mailbox.
--
next prev parent reply other threads:[~2004-12-20 17:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-20 16:46 Robert_Hentosh
2004-12-20 17:56 ` Sami Farin [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-20 15:15 Rik van Riel
2004-12-20 15:23 ` Rik van Riel
2004-12-20 20:54 ` Andrew Morton
2004-12-20 21:27 ` Rik van Riel
2004-12-23 19:21 ` Rik van Riel
2004-12-24 16:01 ` Andrea Arcangeli
2004-12-24 16:22 ` Rik van Riel
2004-12-24 16:40 ` Andrea Arcangeli
2004-12-24 22:12 ` Rik van Riel
2004-12-25 2:07 ` Andrea Arcangeli
2004-12-25 17:59 ` Rik van Riel
2004-12-25 18:36 ` Andrea Arcangeli
2004-12-25 19:07 ` William Lee Irwin III
2004-12-25 20:03 ` Andrea Arcangeli
2004-12-26 3:07 ` William Lee Irwin III
2005-01-02 16:10 ` Andrea Arcangeli
2005-01-02 16:36 ` William Lee Irwin III
2005-01-02 16:53 ` Rik van Riel
2005-01-02 17:21 ` Andrea Arcangeli
2004-12-25 22:03 ` Nikita Danilov
2004-12-26 3:16 ` William Lee Irwin III
2005-01-02 15:11 ` Jens Axboe
2005-01-02 16:18 ` Andrea Arcangeli
2005-01-02 20:03 ` Andrew Morton
2005-01-02 20:25 ` William Lee Irwin III
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=20041220175635.GC7459@m.safari.iki.fi \
--to=7atbggg02@sneakemail.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
all inboxes | Powered by JetHome®