lkml.org 
[lkml]   [2009]   [Apr]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRE: [PATCH 0/8][RFC] IO latency/throughput fixes
Date
> I've added workarounds for 2.6.30 that provide the replace-via-rename
> and replace-via-truncate workarounds for ext3 data=writeback cases.
> See commits e7c8f507 and f7ab34ea.
>
> There won't be an implied fsync for newly created files, yes, but you
> could have crashed 5 seconds earlier, at which point you would have
> lost the newly created file anyway. Replace-via-rename and
> replace-via-truncate solves the problem for applications which are
> editing pre-existing files, which was most of people's complaints
> about depending on data=ordered semantics.

I am not talking about "most" people's complaints. There are use cases for
ext3 far beyond the desktop.

I worked on a user-space library on top of ext3 before on embedded systems.
It may not have been the case for me but I could well imagine where it could
get too clever and depend upon "ordered". You really don't want to silently
corrupt people's data by changing the default. How about security too?
Wasn't that the original reason for "ordered" mode?

Ext3 is supposed to be a stable filesystem, while ext4 is the shiny new
filesystem that gets to do all the exciting experiments. I thought it was
the idea. People do not expect such a change at this stage, for better or
worse. It's great that you can improve its performance, but the performance
problem wasn't introduced yesterday, so if people care they could always
mount it as writeback, but there is no urgency in doing it for them. A
default semantic change is just crazy talk.

Hua




\
 
 \ /
  Last update: 2009-04-06 23:39    [from the cache]
©2003-2011 Jasper Spaans. Advertise on this site