[Lustre-devel] Commit on share
Alex.Zhuravlev at sun.com
Sun Jun 1 09:54:14 PDT 2008
Andreas Dilger wrote:
> I think the commit callbacks should be able to free this data, there
> should never be any such items on an object with di_transno > last_committed.
> Also, isn't it enough to store a single such item per object directly
> on the object? Once we know there is ANY such conflict that is enough
> to invoke COS. For per-object data this can be stored on 1.6 in the
> i_filterdata structure that we can attach onto every server inode.
we don't control inode's lifetime. in order to use i_filterdata we'd have
to pin inode. then we'd have to unpin inode. we can't do this from commit
callback as iput() may cause inode delete. so, we'd have to use special
thread - not that nice.
I believe originally hash table is a intermediate solution for 1.6 and 1.8.
in new server we do have own objects with all needed callbacks to control
data like i_filterdata.
More information about the lustre-devel