From: Mikulas Patocka Subject: Re: [ext3][kernels >= 2.6.20.7 at least] KDE going comatose when FS is under heavy write load (massive starvation) Date: Sat, 28 Apr 2007 22:46:27 +0200 (CEST) Message-ID: References: <1177660767.6567.41.camel@Homer.simpson.net> <20070427013350.d0d7ac38.akpm@linux-foundation.org> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Mike Galbraith , LKML , Linus Torvalds , Jens Axboe , "linux-ext4@vger.kernel.org" To: Andrew Morton Return-path: Received: from artax.karlin.mff.cuni.cz ([195.113.31.125]:34629 "EHLO artax.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753091AbXD1Uq3 (ORCPT ); Sat, 28 Apr 2007 16:46:29 -0400 In-Reply-To: <20070427013350.d0d7ac38.akpm@linux-foundation.org> Sender: linux-ext4-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org > 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