From: Christoph Lameter <cl@linux.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Mel Gorman <mel@csn.ul.ie>,
Stuart Foster <smf.linux@ntlworld.com>,
linux-mm@kvack.org, bugzilla-daemon@bugzilla.kernel.org,
Rik van Riel <riel@redhat.com>,
Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [Bug 42578] Kernel crash "Out of memory error by X" when using NTFS file system on external USB Hard drive
Date: Tue, 14 Feb 2012 14:42:49 -0600 (CST) [thread overview]
Message-ID: <alpine.DEB.2.00.1202141441040.25634@router.home> (raw)
In-Reply-To: <20120214123424.a4162251.akpm@linux-foundation.org>
On Tue, 14 Feb 2012, Andrew Morton wrote:
> On Tue, 14 Feb 2012 14:00:47 -0600 (CST)
> Christoph Lameter <cl@linux.com> wrote:
>
> > On Tue, 14 Feb 2012, Mel Gorman wrote:
> >
> > > Thanks Stuart. Rik, Andrew, should the following be improved in some
> > > way? I did not come to any decent conclusion on what to do with pages in
> > > the inactive list with buffer_head as we are already stripping them when
> > > the pages reach the end of the LRU.
> >
> > We have made the statement in the past that configurations > 8GB on 32
> > bit should not be considered stable or supported? The fact is the more
> > memory you add on 32 bit the less low mem memory is available and the more
> > likely that an OOM will occur for any number of reasons.
>
> I have memories of 16G being usable in earlier kernels.
16G regularly fell over in our environment so we now have an 8G max
restriction for those still using 32 bit.
> Also, if an 8G machine works OK at present, it's only by luck.
> sizeof(buffer_head) is around 100, so it takes 1.6GB of buffer_heads to
> support 8G of 512-byte blocksize pagecache.
Well the slow kernel degradation in operation again. We also require
those 32 bit guys with the 8G limit to run older kernel versions...
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-02-14 20:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-42578-27@https.bugzilla.kernel.org/>
[not found] ` <201201180922.q0I9MCYl032623@bugzilla.kernel.org>
2012-01-19 20:24 ` Andrew Morton
2012-02-10 16:37 ` Mel Gorman
2012-02-10 17:01 ` Rik van Riel
2012-02-14 12:17 ` Mel Gorman
2012-02-11 21:28 ` Stuart Foster
2012-02-14 13:09 ` Mel Gorman
2012-02-14 20:00 ` Christoph Lameter
2012-02-14 20:34 ` Andrew Morton
2012-02-14 20:42 ` Christoph Lameter [this message]
2012-02-14 20:37 ` Andrew Morton
2012-02-15 13:57 ` Mel Gorman
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=alpine.DEB.2.00.1202141441040.25634@router.home \
--to=cl@linux.com \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=riel@redhat.com \
--cc=smf.linux@ntlworld.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