Matt, please see this branch: https://github.com/ffilz/nfs-ganesha/commits/whence-is-name
It allows an FSAL to indicate it takes a name instead of a cookie for whence. In that case, if the protocol requests a cookie that we don't have cached, we will do a readdir from start and scan for the desired cookie. If we happen to have some chunks cached (won't happen until we merge with the memory management stuff), we will skip those (in which case, if we happen to still have the first chunk, we would start our scan from the last known dirent name scanning from the beginning). Some thoughts: Hmm, if the name somehow got removed out from under Ganesha and directory invalidate didn't work, we may need some recovery code. I still need to comment up fsal_api.h... We may want to consider if we can do something less clunky than casting between char * and fsal_cookie_t *... 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
