On Tue, Jan 06, 2015 at 10:46:52AM -0800, Jeff Layton wrote: > So with the current code, layouts are always whole-file? layouts aren't whole-file, but layout recalls are. > Tracking layouts as a lease-like object seems reasonable, but I'm not > 100% thrilled with overloading all of the lease code with this. Perhaps > it should be its own sort of object with a separate API to manage them? > That would also make it easier to support layouts that are not for the > entire file. > > To that end, it might be nice to hold off on taking this until we > deprecate the i_flock list as we can then give layouts their own > list_head in the file_lock_context. It would also make it easier to use > a new sort of object to represent layouts. > > I just cleaned up that patchset last week, and will re-post it soon > once I give it a bit of testing this week. I'm happy to add support to your reworked locks/leases/etc handling for this. As for which one gets merged first I'd say which one is in a mergeable shape earlier. If you're confident to get your rework in ASAP I'm happy to rebase it on top, otherwise doing it the other way around sounds easier. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
