mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "M. Edward (Ed) Borasky" <znmeb@aracnet.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: i686 SMP systems with more then 12 GB ram with 2.4.x kernel, cache buffer bug ?
Date: Tue, 8 Jan 2002 15:28:34 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.33.0201081524360.14913-100000@shell1.aracnet.com> (raw)
In-Reply-To: <1010530993.11323.3.camel@hh2.hhhome.at>

On 9 Jan 2002, Harald Holzer wrote:

> low memory problem:
>
> A Server with 32 GB ram, RH 7.2 and kernel 2.4.17rc2aa2.
> After doing a lot of disc access the system slows down and the system
> dies. Because the system is running out of low memory.
>
> The last kernel logs lines are:
> "kernel: __alloc_pages: 0-order allocation failed (gfp=0x70/0)"
>
> On other kernels then 2.4.17rc2aa2 the oom killer kicks in, or the
> system simply stop responding without any messages.
>
> It looks like that the buffer_heads would fill up the low memory,
> whether there is sufficient memory available or not, as long as
> there is sufficient high memory for caching.
> It seems that the kernel does a good job of releasing dcache or icache,
> but the buffer_heads are filling up the released mem.

In terms of "control knobs", would a limit on page cache size imply a
limit on "buffer_heads", or do we really need the control knob on
"buffer_heads" and not on the page cache? Or would we need both?

-- 
M. Edward "buffer head" Borasky

znmeb@borasky-research.net
http://www.borasky-research.net

What phrase will you *never* hear Candice Bergen use?
"My daddy didn't raise no dummies!"


  reply	other threads:[~2002-01-08 23:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-08 23:03 Harald Holzer
2002-01-08 23:28 ` M. Edward (Ed) Borasky [this message]
2002-01-09  1:25   ` Rik van Riel

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=Pine.LNX.4.33.0201081524360.14913-100000@shell1.aracnet.com \
    --to=znmeb@aracnet.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®