Re: Hi! Is "container" more efficient in terms of I/O op. numbers ...

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 25 May 2012 10:23, NeilBrown <neilb@xxxxxxx> wrote:
[...]
> bitmap metadata certainly can be updated often, but there is no container
> format currently supported which makes use of write-intent bitmaps, so
> thinking about containers for bitmaps is not relevant.

   Well, can it be adopted by allocation sub-array for WIB then, for e. g.?

> If it were, it would make sense to keep the bitmap close to the data that it
> described, so having a container arrangement would not be better than
> individual arrays.  It maybe be worse depending on the particular details.

   Yep, with some kind of updates merging it could be faster, I guess.

   BTW, as it seems the most optimal location of WIB is in the middle
of corresponding datum -- thus
seeks length are always less or equal (datum length 1/2). Have you
considered this layout? :-)

> Does that make sense?

   I hope so. :)

-- 
End of message. Next message?
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux