From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx137.postini.com [74.125.245.137]) by kanga.kvack.org (Postfix) with SMTP id 1CFC66B006C for ; Fri, 11 Jan 2013 03:30:14 -0500 (EST) Received: by mail-ia0-f179.google.com with SMTP id i9so1034766iad.38 for ; Fri, 11 Jan 2013 00:30:13 -0800 (PST) Message-ID: <1357893007.1466.2.camel@kernel.cn.ibm.com> Subject: Re: [RFC] Reproducible OOM with partial workaround From: Simon Jeons Date: Fri, 11 Jan 2013 02:30:07 -0600 In-Reply-To: <20130111000119.8e9bdf5d.akpm@linux-foundation.org> References: <50EF6A2C.7070606@linux.vnet.ibm.com> <201301110146.r0B1kF4T032208@como.maths.usyd.edu.au> <20130111000119.8e9bdf5d.akpm@linux-foundation.org> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Andrew Morton Cc: paul.szabo@sydney.edu.au, dave@linux.vnet.ibm.com, 695182@bugs.debian.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org On Fri, 2013-01-11 at 00:01 -0800, Andrew Morton wrote: > On Fri, 11 Jan 2013 12:46:15 +1100 paul.szabo@sydney.edu.au wrote: > > > > ... I don't believe 64GB of RAM has _ever_ been booted on a 32-bit > > > kernel without either violating the ABI (3GB/1GB split) or doing > > > something that never got merged upstream ... > > > > Sorry to be so contradictory: > > > > psz@como:~$ uname -a > > Linux como.maths.usyd.edu.au 3.2.32-pk06.10-t01-i386 #1 SMP Sat Jan 5 18:34:25 EST 2013 i686 GNU/Linux > > psz@como:~$ free -l > > total used free shared buffers cached > > Mem: 64446900 4729292 59717608 0 15972 480520 > > Low: 375836 304400 71436 > > High: 64071064 4424892 59646172 > > -/+ buffers/cache: 4232800 60214100 > > Swap: 134217724 0 134217724 > > psz@como:~$ > > > > (though I would not know about violations). > > > > But OK, I take your point that I should move with the times. > > Check /proc/slabinfo, see if all your lowmem got eaten up by buffer_heads. > > 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. > > Alternatively, use a filesystem which doesn't attach buffer_heads to > dirty pages. xfs or btrfs, perhaps. > Hi Andrew, What's the meaning of attaching buffer_heads to dirty pages? > -- > 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: email@kvack.org -- 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: email@kvack.org