[Lustre-devel] storing SOM epoch in EA

Nikita Danilov Nikita.Danilov at Sun.COM
Tue Feb 19 08:21:19 PST 2008

Alex Zhuravlev writes:
 > Yuriy Umanets wrote:
 > > EA is separate block is evil. It makes things slow.
 > we have fast EAs (stored in inode, this is why we make them large) for years.
 > > Well, it did not in cmd3 :)
 > if it isn't stored in inode, it's a seek.

One possible point here is that OSD has to do fid->ino translation
anyway, and it makes sense to use the same index to store other
information besides inode number. That is, we can use "object index" iam
file to map fid into (ino, gen, ioepoch, LOV, ...) records, and this
would not cause any additional seeks. The downside here is that object
index is so heavily used, that making its records larger is going to
increase the amount of IO significantly, so it only worth to place there
things that we are absolutely sure will be needed for every inode.

 > thanks, Alex


More information about the lustre-devel mailing list