linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Rik van Riel <riel@humbolt.geo.uu.nl>
Cc: Linux MM <linux-mm@kvack.org>, Stephen Tweedie <sct@redhat.com>
Subject: Re: bdflush defaults bugreport
Date: Mon, 13 Sep 1999 19:02:59 +0100 (BST)	[thread overview]
Message-ID: <14301.15443.303167.898233@dukat.scot.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.10.9909050953540.247-100000@mirkwood.dummy.home>

Hi,

On Sun, 5 Sep 1999 09:58:56 +0200 (CEST), Rik van Riel
<riel@humbolt.geo.uu.nl> said:

> yesterday evening I've seen a 32MB machine failing to install because
> mke2fs was killed due to memory shortage -- memory shortage due to
> a too large number of dirty blocks (max 40% by default).

In the past, such problems were mainly due to the refile_buffer() code
not limiting the write rate of heavy buffer cache writes more than
anything else.

> Lowering the number to 1% solved all problems, so I guess we should
> lower the number in the kernel to something like 10%, which should
> be _more_ than enough since the page cache can now be dirty too...

That is not a clean solution: it's just imposing an unnecessary
performance on the whole cache when the problem probably lies
elsewhere.  

> Btw, the problem happened on a 2.2.10 machine

In 2.2, the page cache cannot be dirty in this sense.

--Stephen
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/

  parent reply	other threads:[~1999-09-13 18:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-05  7:58 Rik van Riel
1999-09-05  8:55 ` [2.2.12 PATCH] " Benjamin C.R. LaHaise
1999-09-13 18:06   ` Stephen C. Tweedie
1999-09-13 18:02 ` Stephen C. Tweedie [this message]
     [not found]   ` <Pine.LNX.3.96.990913140636.29128A-100000@kanga.kvack.org>
1999-09-13 20:24     ` Stephen C. Tweedie

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=14301.15443.303167.898233@dukat.scot.redhat.com \
    --to=sct@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=riel@humbolt.geo.uu.nl \
    /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