[Gluster-devel] Storing list of dentries of children in parent inode

Vijay Bellur vbellur at redhat.com
Fri Jun 29 06:55:22 UTC 2018

On Wed, Jun 27, 2018 at 10:15 PM Raghavendra Gowdappa <rgowdapp at redhat.com>

> All,
> There is a requirement in write-behind where during readdirp we may have
> to invalidate iatts/stats of some of the children of the directory [1]. For
> lack of better alternatives I added a dentry list to parent inode which
> contains all children that've been linked (through lookup or readdirp on
> directory). I myself am not too comfortable with this solution as it might
> eat up significant memory for large directories.
> Thoughts?

Reading [2] makes me wonder if write-behind is the appropriate place for
this change. Shouldn't md-cache be made aware of inode generations or
something similar?


[2] https://bugzilla.redhat.com/show_bug.cgi?id=1512691#c18

> [1] https://review.gluster.org/20413
> regards,
> Raghavendra
> _______________________________________________
> Gluster-devel mailing list
> Gluster-devel at gluster.org
> http://lists.gluster.org/mailman/listinfo/gluster-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/gluster-devel/attachments/20180628/05037822/attachment.html>

More information about the Gluster-devel mailing list