On Tue, 26 Sep 2017, Jeff Layton wrote: > In order to get the correct semantics for a delegation or oplock, we > need to be able to break delegations on open. Can you explain this part? How do the delegation/oplock semantics relate to open(2)? I would assume they are related to reads and writes (and data consistency). Unless it's a CIFS thing? sage -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
