To follow up on the development on an FSAL for S3, I have some doubts
and questions I'd like to share.
Apart from its full path, S3 doesn't have the concept of file
descriptor, I mean, there's nothing else
than the full path that I can provide to S3 in order to get attribute
of content of a specific object.
I have some doubts regarding the implementation of the S3 fsal object
handle (s3_fsal_obj_handle).
Should s3_fsal_obj_handle be very simple, for example should it
only contain a key that maps to the full S3 filename, in an key-value
store.
Or on the contrary, should the handle implement a tree like structure,
like I saw in FSAL_MEM?
Or something in between, but what?
Having a very simple handle has some advantages but may require some
more frequent network calls,
for example readdir won't have any kind of information about the
content of the directory.
Having a whole tree-like structure in the handle would allow to have
direct access to directory content,
but isn't that the role of ganesha cache to do that?
My questions probably shows that I have problems to understand the
responsability of my FSAL implementation
regarding the cache. Who does what, what doesn't do what?
Good evening,
Aurélien
------------------------------------------------------------------------------
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
