[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4631EEFE.7060309@clusterfs.com>
Date: Fri, 27 Apr 2007 18:09:26 +0530
From: Manoj Joseph <manoj@...sterfs.com>
To: Marat Buharov <marat.buharov@...il.com>
CC: Andrew Morton <akpm@...ux-foundation.org>,
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)
Marat Buharov wrote:
> On 4/27/07, Andrew Morton <akpm@...ux-foundation.org> wrote:
>> 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.
>
> So, if having fake fsync() and fdatasync() is pleasurable for laptop
> and desktop, may be it's time to add option into Kconfig which
> disables normal fsync behaviour in favor of robust desktop?
Sure, a noop fsync/fdatasync would speed up some things. And I am sure
Andrew Morton knew what he was doing and the consequences.
But unless you care nothing about your data, you should not do it. It is
as simple as that. No, it does not give you a robust desktop!!
-Manoj
--
Manoj Joseph
http://kerneljunkie.blogspot.com/
-
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