FUJITA Tomonori wrote:
On Thu, 21 Aug 2008 20:33:03 +1000
"ronnie sahlberg" <ronniesahlberg@xxxxxxxxx> wrote:
To support variable block, metadata needs to be kept for each block.
Since this will be a structure of a handful of bytes for each of
possibly bilions of blocks extended attributes might be suboptimal
for storing this partucular metadata.
Due to the massive amount of metadata required for the
"per-block-metadata" you probably want a non-extended attributes
method for that. separate file?
Mark, can you summarize the requirements of the metadata of ssc?
- how much bytes does the metadata need?
- can we know how much bytes we will need in the future when we create
a ssc file? (or we need to enlarge the metadata as the need arises?)
Sure.. But I've got my head in the persistent reserve code at the moment. I'll go back to the bs_ssc/bs_tape once I get something useful with the persistent reserve (or hit a road-block).
Cheers
Mark
feel free to add new items.
For all other types of metadata, which may be shared with MMC, which
is also a very small amount of metadata, like media-serial-number,
barcode, mam-data etc for those i think extended attributes are
best.
--
To unsubscribe from this list: send the line "unsubscribe stgt" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe stgt" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
