[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0704282242280.16099@artax.karlin.mff.cuni.cz>
Date: Sat, 28 Apr 2007 22:46:27 +0200 (CEST)
From: Mikulas Patocka <mikulas@...ax.karlin.mff.cuni.cz>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Mike Galbraith <efault@....de>,
LKML <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Jens Axboe <jens.axboe@...cle.com>,
"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: Re: [ext3][kernels >= 2.6.20.7 at least] KDE going comatose when FS
is under heavy write load (massive starvation)
> hm, fsync.
>
> Aside: why the heck do applications think that their data is so important
> that they need to fsync it all the time. I used to run a kernel on my
> laptop which had "return 0;" at the top of fsync() and fdatasync(). Most
> pleasurable.
>
> But wedging for 20 minutes is probably excessive punishment.
I most wonder, why vim fsyncs its swapfile regularly (blocking typing
during that) and doesn't fsync the resulting file on :w :-/
Mikulas
-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists