fsal api has changed quite a bit and documentation is seriously lacking about nfs-ganesha HOT 6 OPEN

Is there any chance to prioritize this? As a FSAL author it is nearly impossible to figure out what to do.
Thanks!

from nfs-ganesha.

Most or all of those functions are doxygen documented in fsal/commonlib.c. Basically all of our API-level documentation is done via doxygen comments on the function's implementation.

from nfs-ganesha.

I am mostly concerned about these:

• fsal_start_io
• fsal_start_global_io
• fsal_complete_io
• fsal_start_fd_work
• fsal_complete_fd_work
• insert_fd_lru
• Also the fsal_obj_handle::obj_lock

All fsals that ship with ganesha call most of these, so it appears to me this is definitely part of the FSAL api. It would greatly help to have a doc or comments on the header file or whatever that describes global file descriptors, and FD lru. How is this used? What is the policy? Etc.

from nfs-ganesha.

There is some in code documentation on those in commonlib.c.

I can try and find some time to improve the documentation of all of that...

from nfs-ganesha.

Perhaps the most useful thing would be one or two pages on what those functions are about, and not necessarily a bunch of comments on each of the functions (although that would also be super useful).

What is this "fd lru" thing?
What is bump fd lru for?
In fact, what IS an fd?
How do I configure fd lru in ganesha config?
etc.....

Please keen in mind developers that write their own FSAL.

from nfs-ganesha.

I'm working on, and will submit tomorrow, a patch that adds more description about fsal_fd and the API with the definition of struct fsal_fd.

As to how to configure, we don't really have much suggestion for that, but I will document the mdcache parameters that are passed onto the fd_lru.

The most important ones are the FD_Limit_Percent, FD_HWMark_Percent, and FD_LWMark_Percent that govern the size of the fd_lru based on a percentage of the process RLIMIT_NOFILE (ulimit -n)

from nfs-ganesha.