I'm taking a stab at converting ceph to use the netfs write helpers. One thing I'm seeing though is that the kclient takes great care to write back data to the OSDs in order of snap context age, such that an older snapc will get written back before a newer one. With the netfs helpers, that may not happen quite as naturally. We may end up with it trying to flush data for a newer snapc ahead of the older one. My question is: is that necessarily a problem? We'd be sending along the correct info from the capsnap for each snapc, which seems like it should be sufficient to ensure that the writes get applied correctly. If we were to send these out of order, what would break and how? -- Jeff Layton <jlayton@xxxxxxxxxx> _______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
