From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: i/o stalls on 2.4.14-pre3 with ext3
Date: Tue, 30 Oct 2001 04:12:00 +0000 (UTC) [thread overview]
Message-ID: <9rl9ag$7su$1@penguin.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0110292120340.16895-100000@admin> <3BDE161A.D8289730@zip.com.au>
In article <3BDE161A.D8289730@zip.com.au>,
Andrew Morton <akpm@zip.com.au> wrote:
>
>ext3's problem is that it is unable to react to VM pressure
>for metadata (buffercache) pages. Once upon a time it did
>do this, but we backed it out because it involved mauling
>core kernel code. So at present we only react to VM pressure
>for data pages.
Note that the new VM has some support in place for the low-level
filesystem reacting to VM pressure. In particular, one thing the fs can
do is to look at the PG_launder bit (for pages) and PG_launder bit (for
buffers), to figure out if the IO is due to memory pressure.
A "sync" will not have the launder bit set, while something started due
to VM pressure will have the bits set.
>Then again, maybe something got broken in the buffer writeout
>code or something.
There are two really silly request bugs in 2.4.14-pre3. I'd suggest
trying pre5 which cleans up other things too, but even more notably
should fix the request queue thinkos.
Linus
next prev parent reply other threads:[~2001-10-30 4:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-30 2:36 i/o stalls on 2.4.14-pre3 with ext3 David Mansfield
2001-10-30 2:53 ` Andrew Morton
2001-10-30 3:44 ` David Mansfield
2001-10-30 4:12 ` Linus Torvalds [this message]
2001-10-30 6:40 ` Andrew Morton
2001-10-30 7:34 ` Linus Torvalds
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='9rl9ag$7su$1@penguin.transmeta.com' \
--to=torvalds@transmeta.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.