From: paul.szabo@sydney.edu.au
To: akpm@linux-foundation.org
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: Sat, 12 Jan 2013 14:24:07 +1100 [thread overview]
Message-ID: <201301120324.r0C3O7DY015947@como.maths.usyd.edu.au> (raw)
In-Reply-To: <20130111123149.c3232a96.akpm@linux-foundation.org>
Dear Andrew,
>>> Check /proc/slabinfo, see if all your lowmem got eaten up by buffer_heads.
>> Please see below ...
> ... Was this dump taken when the system was at or near oom?
No, that was a "quiescent" machine. Please see a just-before-OOM dump in
my next message (in a little while).
> Please send a copy of the oom-killer kernel message dump, if you still
> have one.
Please see one in next message, or in
http://bugs.debian.org/695182
>> I tried setting dirty_ratio to "funny" values, that did not seem to
>> help.
> Did you try setting it as low as possible?
Probably. Maybe. Sorry, cannot say with certainty.
>> Did you notice my patch about bdi_position_ratio(), how it was
>> plain wrong half the time (for negative x)?
> Nope, please resend.
Quoting from
http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=101;att=1;bug=695182
:
...
- In bdi_position_ratio() get difference (setpoint-dirty) right even
when it is negative, which happens often. Normally these numbers are
"small" and even with left-shift I never observed a 32-bit overflow.
I believe it should be possible to re-write the whole function in
32-bit ints; maybe it is not worth the effort to make it "efficient";
seeing how this function was always wrong and we survived, it should
simply be removed.
...
--- mm/page-writeback.c.old 2012-10-17 13:50:15.000000000 +1100
+++ mm/page-writeback.c 2013-01-06 21:54:59.000000000 +1100
[ Line numbers out because other patches not shown ]
...
@@ -559,7 +578,7 @@ static unsigned long bdi_position_ratio(
* => fast response on large errors; small oscillation near setpoint
*/
setpoint = (freerun + limit) / 2;
- x = div_s64((setpoint - dirty) << RATELIMIT_CALC_SHIFT,
+ x = div_s64(((s64)setpoint - (s64)dirty) << RATELIMIT_CALC_SHIFT,
limit - setpoint + 1);
pos_ratio = x;
pos_ratio = pos_ratio * x >> RATELIMIT_CALC_SHIFT;
...
Cheers, Paul
Paul Szabo psz@maths.usyd.edu.au http://www.maths.usyd.edu.au/u/psz/
School of Mathematics and Statistics University of Sydney Australia
--
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>
next prev parent reply other threads:[~2013-01-12 3:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 21:58 paul.szabo
2013-01-10 23:12 ` Dave Hansen
2013-01-11 0:46 ` paul.szabo
2013-01-11 1:26 ` Dave Hansen
2013-01-11 1:46 ` paul.szabo
2013-01-11 8:01 ` Andrew Morton
2013-01-11 8:30 ` Simon Jeons
2013-01-11 11:51 ` paul.szabo
2013-01-11 20:31 ` Andrew Morton
2013-01-12 3:24 ` paul.szabo [this message]
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=201301120324.r0C3O7DY015947@como.maths.usyd.edu.au \
--to=paul.szabo@sydney.edu.au \
--cc=695182@bugs.debian.org \
--cc=akpm@linux-foundation.org \
--cc=dave@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--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