Hi Miklos, Will you apply my previous patch "ovl: Use macros to present ovl_xattr"? These two patches(previous one and this one) are based on branch *overlayfs-current* and conflict with each other.
I don't know which branch I should use, overlayfs-current or overlayfs-next. How could I join the development? By the way, do you think we can make use of "kmem_cache" to manage "struct ovl_entry"? I think it will speedup operations like *ls*. I saw your work about multi-layer support. The size of "struct ovl_entry" will be variable. In addition, some free paths of ovl_entry rely on RCU. So maybe it's not easy. Thanks~! Hu -- To unsubscribe from this list: send the line "unsubscribe linux-unionfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
