From: Andrew Morton <akpm@linux-foundation.org>
To: paul.szabo@sydney.edu.au
Cc: 695182@bugs.debian.org, dave@linux.vnet.ibm.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [RFC] Reproducible OOM with partial workaround
Date: Fri, 11 Jan 2013 12:31:49 -0800 [thread overview]
Message-ID: <20130111123149.c3232a96.akpm@linux-foundation.org> (raw)
In-Reply-To: <201301111151.r0BBpZt1023276@como.maths.usyd.edu.au>
On Fri, 11 Jan 2013 22:51:35 +1100
paul.szabo@sydney.edu.au wrote:
> Dear Andrew,
>
> > Check /proc/slabinfo, see if all your lowmem got eaten up by buffer_heads.
>
> Please see below: I do not know what any of that means. This machine has
> been running just fine, with all my users logging in here via XDMCP from
> X-terminals, dozens logged in simultaneously. (But, I think I could make
> it go OOM with more processes or logins.)
I'm counting 107MB in slab there. Was this dump taken when the system
was at or near oom?
Please send a copy of the oom-killer kernel message dump, if you still
have one.
> > If so, you *may* be able to work around this by setting
> > /proc/sys/vm/dirty_ratio really low, so the system keeps a minimum
> > amount of dirty pagecache around. Then, with luck, if we haven't
> > broken the buffer_heads_over_limit logic it in the past decade (we
> > probably have), the VM should be able to reclaim those buffer_heads.
>
> I tried setting dirty_ratio to "funny" values, that did not seem to
> help.
Did you try setting it as low as possible?
> Did you notice my patch about bdi_position_ratio(), how it was
> plain wrong half the time (for negative x)?
Nope, please resend.
> Anyway that did not help.
>
> > Alternatively, use a filesystem which doesn't attach buffer_heads to
> > dirty pages. xfs or btrfs, perhaps.
>
> Seems there is also a problem not related to filesystem... or rather,
> the essence does not seem to be filesystem or caches. The filesystem
> thing now seems OK with my patch doing drop_caches.
hm, if doing a regular drop_caches fixes things then that implies the
problem is not with dirty pagecache. Odd.
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: paul.szabo@sydney.edu.au
Cc: 695182@bugs.debian.org, dave@linux.vnet.ibm.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [RFC] Reproducible OOM with partial workaround
Date: Fri, 11 Jan 2013 12:31:49 -0800 [thread overview]
Message-ID: <20130111123149.c3232a96.akpm@linux-foundation.org> (raw)
In-Reply-To: <201301111151.r0BBpZt1023276@como.maths.usyd.edu.au>
On Fri, 11 Jan 2013 22:51:35 +1100
paul.szabo@sydney.edu.au wrote:
> Dear Andrew,
>
> > Check /proc/slabinfo, see if all your lowmem got eaten up by buffer_heads.
>
> Please see below: I do not know what any of that means. This machine has
> been running just fine, with all my users logging in here via XDMCP from
> X-terminals, dozens logged in simultaneously. (But, I think I could make
> it go OOM with more processes or logins.)
I'm counting 107MB in slab there. Was this dump taken when the system
was at or near oom?
Please send a copy of the oom-killer kernel message dump, if you still
have one.
> > If so, you *may* be able to work around this by setting
> > /proc/sys/vm/dirty_ratio really low, so the system keeps a minimum
> > amount of dirty pagecache around. Then, with luck, if we haven't
> > broken the buffer_heads_over_limit logic it in the past decade (we
> > probably have), the VM should be able to reclaim those buffer_heads.
>
> I tried setting dirty_ratio to "funny" values, that did not seem to
> help.
Did you try setting it as low as possible?
> Did you notice my patch about bdi_position_ratio(), how it was
> plain wrong half the time (for negative x)?
Nope, please resend.
> Anyway that did not help.
>
> > Alternatively, use a filesystem which doesn't attach buffer_heads to
> > dirty pages. xfs or btrfs, perhaps.
>
> Seems there is also a problem not related to filesystem... or rather,
> the essence does not seem to be filesystem or caches. The filesystem
> thing now seems OK with my patch doing drop_caches.
hm, if doing a regular drop_caches fixes things then that implies the
problem is not with dirty pagecache. Odd.
next prev parent reply other threads:[~2013-01-11 20:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 21:58 [RFC] Reproducible OOM with partial workaround paul.szabo
2013-01-10 21:58 ` paul.szabo
2013-01-10 23:12 ` Dave Hansen
2013-01-10 23:12 ` Dave Hansen
2013-01-11 0:46 ` paul.szabo
2013-01-11 0:46 ` paul.szabo
2013-01-11 1:26 ` Dave Hansen
2013-01-11 1:26 ` Dave Hansen
2013-01-11 1:46 ` paul.szabo
2013-01-11 1:46 ` paul.szabo
2013-01-11 8:01 ` Andrew Morton
2013-01-11 8:01 ` Andrew Morton
2013-01-11 8:30 ` Simon Jeons
2013-01-11 8:30 ` Simon Jeons
2013-01-11 11:51 ` paul.szabo
2013-01-11 11:51 ` paul.szabo
2013-01-11 20:31 ` Andrew Morton [this message]
2013-01-11 20:31 ` Andrew Morton
2013-01-12 3:24 ` paul.szabo
2013-01-12 3:24 ` paul.szabo
2013-01-11 16:04 ` Dave Hansen
2013-01-11 16:04 ` Dave Hansen
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=20130111123149.c3232a96.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=695182@bugs.debian.org \
--cc=dave@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=paul.szabo@sydney.edu.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.