> We have been working with 2.3-stable release for a while now. We have > stabilised our FSAl layer recently and wanted to move to 2.4. I can see that > there are a lot of design changes as well which went into 2.4. How is the FSAL > layer impacted with these changes? Are there any semantic changes? > > Also, the extended support functions seem to be optional. So, is it a major > impact on FSAL layer if support_ex callbacks are not implemented?
The non-extended API functions will be removed in 2.6 (consider them deprecated in 2.5). There is a document that describes most of the changes: https://docs.google.com/document/d/1pOpN7Ea3zK4Yf5aIK-rTVxVC91Y7HdjGpECqAW-G cd4/edit?usp=sharing The biggest impact is that the FSAL becomes more closely involved in state (locks and share reservations) that previously. One big advantage for any FSAL that can support share reservations in its underlying filesystem is being able to do so in cooperation with the protocol layer and in a single FSAL call. It is possible to have an FSAL that has minimal support of the extended API (look at the FSAL_PROXY implementation in 2.5). If you do actually have something akin to an open file (whether it is a POSIX file descriptor or something else), it is possible to still use a global open file resource for that and not have per-state open file resources, however, there is an advantage that the FSAL has more control over how that open file resource is managed which can actually make it MORE useful (the old mechanism relied on the cache inode layer protecting access with the content_lock, but not all FSAL methods that potentially could use the open file resource were called with the content_lock, for example setattrs). There is also a significant change in attribute management, but I believe that is nothing but an improvement. I'm happy to discuss any concerns or issues you have in making the transition. Frank --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Nfs-ganesha-devel mailing list Nfs-ganesha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs-ganesha-devel
