Tmap simply places the keys and values in order in the normal object data. The only advantage of tmap over simply writing the values out sequentially using normal operations is that you don't need to read in the the tmap to do an insertion. Tmap probably shouldn't be used at this stage. Omaps are stored separately in a leveldb store and can be used independently of the actual object contents. Xattrs are stored either as filesystem xattrs or in the leveldb store alongside the omap depending on: filestore_xattr_use_omap, filestore_max_inline_xattr_size, and filestore_max_inline_xattrs. -Sam On Sun, Aug 26, 2012 at 10:09 AM, Noah Watkins <jayhawk@xxxxxxxxxxx> wrote: > Would anyone mind giving a short overview of the difference between > tmap, omap, and xattrs, and the physical layout of these with respect > to the object payload? > > Thanks, > Noah > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" 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 ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
