Thread (23 messages) 23 messages, 5 authors, 2008-08-18

Re: Btrfs v0.16 released

From: Theodore Tso <tytso@mit.edu>
Date: 2008-08-09 01:19:05
Also in: linux-fsdevel, lkml

Possibly related (same subject, not in this thread)

On Fri, Aug 08, 2008 at 11:56:25PM +0200, Andi Kleen wrote:
quoted
So, the mirroring turns a single large write into two large writes.
Definitely not free, but always a fixed cost.
Thanks for the explanation and the numbers. I see that's the advantage of 
copy-on-write that you can actually always cluster the metadata together and 
get always batched IO this way and then afford to do more of it. 

Still wondering what that will do to read seekiness.
In theory, if the elevator was smart enough, it could actually help
read seekiness; there are two copies of the metadata, and it shouldn't
matter which one is fetched.  So I could imagine a (hypothetical) read
request which says, "please give me the contents of block 4500 or
75000000 --- I don't care which, if the disk head is closer to one end
of the disk or another, use whichever one is most convenient".  Our
elevator algorithms are currently totally unable to deal with this
sort of request, and if SSD's are going to be coming on line as
quickly as some people are claiming, maybe it's not worth it to try to
implement that kind of thing, but at least in theory it's something
that could be done....

						- Ted
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help