On Wed, Nov 26, 2014 at 10:07 AM, hujianyang <hujianyang@xxxxxxxxxx> wrote: > 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? If it's a bugfix, then do it against -current. If it's a cleanup patch, like the one you did, do it against -next. > 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. With the multi-layer support in overlayfs-next "struct ovl_entry" becomes variable sized, so we can't use kmem_cache for it. Thanks, Miklos -- To unsubscribe from this list: send the line "unsubscribe linux-unionfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
