All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: David Mansfield <david@cobite.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: i/o stalls on 2.4.14-pre3 with ext3
Date: Mon, 29 Oct 2001 18:53:14 -0800	[thread overview]
Message-ID: <3BDE161A.D8289730@zip.com.au> (raw)
In-Reply-To: <Pine.LNX.4.21.0110292120340.16895-100000@admin>

David Mansfield wrote:
> 
> I tried out 2.4.14-pre3 plus the ext3 patch from Andrew Morton and
> encountered some strange I/O stalls.   I was doing a 'cvs tag' of my local
> kernel-cvs repository, which generates a lot of read/write traffic in a
> single process.

hmm..  Thanks - I'll do some metadata-intensive testing.

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.

Now that metadata pages have a backing address_space, I think we
can again allow ext3 to react to VM pressure against metadata.
It'll take some more mauling, but it's good mauling ;)

Then again, maybe something got broken in the buffer writeout
code or something.

Is this repeatable? 

	while true
	do
		cvs tag foo
		cvs tag -d foo
	done

If so, can you run `top' in parallel, see if there's
anything suspicious happening?

  reply	other threads:[~2001-10-30  2:58 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 [this message]
2001-10-30  3:44   ` David Mansfield
2001-10-30  4:12   ` Linus Torvalds
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=3BDE161A.D8289730@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=david@cobite.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.