public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Richard Guenther <rguenth@tat.physik.uni-tuebingen.de>
Cc: Oliver Paukstadt <pstadt@stud.fh-heilbronn.de>,
	Matti Aarnio <matti.aarnio@zmailer.org>,
	Linux-Kernel <linux-kernel@vger.kernel.org>,
	linux-raid@vger.kernel.org
Subject: Re: 2.4.17 RAID-1 EXT3  reliable to hang....
Date: Mon, 07 Jan 2002 02:09:29 -0800	[thread overview]
Message-ID: <3C3973D9.CF689345@zip.com.au> (raw)
In-Reply-To: <Pine.LNX.4.33.0201070933590.4076-100000@lola.stud.fh-heilbronn.de> <Pine.LNX.4.33.0201071047410.17279-100000@bellatrix.tat.physik.uni-tuebingen.de>

Richard Guenther wrote:
> 
> On Mon, 7 Jan 2002, Oliver Paukstadt wrote:
> 
> > Heavy traffic on ext3 seems to cause short system freezes.
> 
> I see dropped frames while watching TV (bttv chip, xawtv in overlay mode,
> XFree 4.1.0)
> since I use ext3 (2.4.16&17). Always during disk activity (IDE, umask irq
> and dma enabled). From what I know the bttv driver does it seems to loose
> interrupts!? This doesnt happen with ext2.

ext3 never blocks interrupts.  It _may_ cause increased interrupt
latency than ext2 by the very large linear writes which it does.  These
may cause other parts of the kernel to block interrupts for longer.

However, more likely that it's a scheduling latency problem.  Sigh.
I spent *ages* on the ext3 buffer writeout code and it's still not
ideal.  Can you test with this patch applied?

http://www.zipworld.com.au/~akpm/linux/2.4/2.4.18-pre1/mini-ll.patch

It should go into 2.4.17 OK.

> ...
> By any chance, is some global lock held during any IO intensive part of
> ext3?

Yes, a couple.  But on uniprocessor it's more a matter of the kernel
failing to context switch promptly.

-

  reply	other threads:[~2002-01-07 10:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-04 14:36 2.4.17 RAID-1 EXT3 reliable to hang Matti Aarnio
2002-01-07  8:00 ` Matti Aarnio
2002-01-07  8:19   ` Andrew Morton
2002-01-07  8:38     ` Matti Aarnio
2002-01-07  8:39     ` Oliver Paukstadt
2002-01-07  8:49       ` Andrew Morton
2002-01-07  9:51       ` Richard Guenther
2002-01-07 10:09         ` Andrew Morton [this message]
2002-01-07 10:33           ` Richard Guenther
2002-01-20 17:31           ` Matti Aarnio
2002-01-20 19:24             ` John Jasen
2002-01-20 19:57               ` Matti Aarnio
2002-01-21  0:22                 ` Oliver Xymoron
2002-01-07 13:45         ` Alan Cox

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=3C3973D9.CF689345@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=matti.aarnio@zmailer.org \
    --cc=pstadt@stud.fh-heilbronn.de \
    --cc=rguenth@tat.physik.uni-tuebingen.de \
    /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