[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120418160717.GE5916@thunk.org>
Date: Wed, 18 Apr 2012 12:07:17 -0400
From: Ted Ts'o <tytso@....edu>
To: Dave Chinner <david@...morbit.com>
Cc: Eric Sandeen <sandeen@...hat.com>,
Ric Wheeler <rwheeler@...hat.com>,
Zheng Liu <gnehzuil.liu@...il.com>,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-ext4@...r.kernel.org, Zheng Liu <wenqing.lz@...bao.com>
Subject: Re: [RFC][PATCH 0/3] add FALLOC_FL_NO_HIDE_STALE flag in fallocate
On Wed, Apr 18, 2012 at 01:02:08PM +1000, Dave Chinner wrote:
> In actual fact, on my 12 disk RAID0 array, XFS is faster with
> unwritten extents *enabled* than when hacked to turn them off.
Can you explain why this is the case? It seems... counterintuitive.
The only explanation I can think of is that your code paths when
unwritten extents are disabled haven't been optimized, in which case
the comparison between using and not using unwritten extents might not
be valid.
Is there anything going on other than _not_ mutating the extent tree
(and all of the logical journaling that would go along with it)?
Hacking to turn them off means it should be doing *less* work, so I
would expect at worst it would be the same speed as using extent
written extents. If it's faster to use unwritten extents, something
very wierd must be going on....
- Ted
--
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