[Lustre-devel] storing SOM epoch in EA
Yuriy Umanets
Yury.Umanets at Sun.COM
Tue Feb 19 07:10:08 PST 2008
Alex Zhuravlev wrote:
> Yuriy Umanets wrote:
>
>> Yes, this is what I understand as well. And we were discussing that EA
>> approach has some downsides. In fact what you propose, that is, store it
>> in EA is logical taking into account that epoch is kind of extension to
>> inode fields. It is property of inode-object. It is logical to store it
>> with inode, I see your point. But as we saw, this has/may have some
>> downsides which may be solved with IAM. Just take this in mind when you
>> think/work on it. I do not see why IAM is such a bad here.
>>
>
> 1) additional seek(s)
> 2) shared structure (additional cost on concurrent access)
> 3) inode is already 512 bytes
>
>
Agreed, but this is all not measured and may happen that IAM is not
worse but more handy in many respects.
Thanks.
> thanks, Alex
>
>
>
> _______________________________________________
> Lustre-devel mailing list
> Lustre-devel at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-devel
>
--
umka
More information about the lustre-devel
mailing list