Added some documentation of fuse internals.

This commit is contained in:
Nikolaus Rath
2017-09-17 09:35:43 +01:00
parent cfdca8c6a0
commit 109ab4fa53
3 changed files with 17 additions and 0 deletions
+2
View File
@@ -795,6 +795,8 @@ DOCSET_BUNDLE_ID = org.doxygen.Project
HTML_DYNAMIC_SECTIONS = YES
HTML_EXTRA_FILES = doc/fast17-vangoor.pdf
# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
# be used to specify the file name of the resulting .chm file. You
# can add a path in front of the file if the result should not be
Binary file not shown.
+15
View File
@@ -35,5 +35,20 @@ href="files.html">examples</a> directory. A good starting point are
hello.c (for the high-level API) and hello_ll.c (for the low-level
API).
## FUSE internals ##
The authoritative source of information about libfuse internals
(including the protocol used for communication with the FUSE kernel
module) is the source code.
However, some people have kindly documented different aspects of FUSE
in a more beginner friendly way. While this information is
increasingly out of date, it still provides a good overview:
- Bharat Vangoor et al have included an overview of the FUSE internals
in a <a href="fast17-vangoor.pdf">paper evaluating FUSE performance</a>.
- Some documentation of the kernel-userspace protocol is available on
the <a href="https://github.com/libfuse/libfuse/wiki/">libfuse wiki</a>.
*/