[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1177741953.6268.18.camel@Homer.simpson.net>
Date:	Sat, 28 Apr 2007 08:32:32 +0200
From:	Mike Galbraith <efault@....de>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Jens Axboe <jens.axboe@...cle.com>
Subject: Re: [ext3][kernels >= 2.6.20.7 at least] KDE going comatose when
	FS is under heavy write load (massive starvation)
On Sat, 2007-04-28 at 06:25 +0200, Mike Galbraith wrote:
> On Fri, 2007-04-27 at 08:18 -0700, Linus Torvalds wrote:
> 
> > Actually, you don't need to apply the patch - just do
> > 
> > 	echo 5 > /proc/sys/vm/dirty_background_ratio
> > 	echo 10 > /proc/sys/vm/dirty_ratio
> 
> That seems to have done the trick.  Amarok and GUI aren't exactly speed
> demons while writeout is happening, but they are not hanging for
> eternities.
As promised, I tested with a kernel that I know for fact that I have
tested heavy IO on previously, and behavior was identically horrid, so
it's not something new that snuck in ~recently, my disk just got a _lot_
fuller in the meantime (12k mp3s munch a lot).
I also verified that I don't need to use the dirty data restrictions
with ext2, all is just peachy using stock settings.  Amarok switches
songs quickly, and GUI doesn't hang.  Behavior is that expected of a
heavily loaded IO subsystem, and is 1000% better than ext3 with my very
full disk.
Journaling is very nice, but I think I'll be much better off without it
responsiveness wise.
	-Mike
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
Powered by blists - more mailing lists
 
