aboutsummaryrefslogtreecommitdiffstats
path: root/include/fuse_common.h
AgeCommit message (Collapse)AuthorLines
2023-01-28Install a the configure_file (config.h) and use in headersBernd Schubert-0/+1
This addresses: https://github.com/libfuse/libfuse/issues/724 HAVE_LIBC_VERSIONED_SYMBOLS configures the library if to use versioned symbols and is set at meson configuration time. External filesystems (the main target, actually) include fuse headers and the preprocessor then acts on HAVE_LIBC_VERSIONED_SYMBOLS. Problem was now that 'config.h' was not distributed with libfuse and so HAVE_LIBC_VERSIONED_SYMBOLS was never defined with external tools and the preprocessor did the wrong decision. This commit also increases the the minimal meson version, as this depends on meson feature only available in 0.50 <quote 'meson' > WARNING: Project specifies a minimum meson_ version '>= 0.42' but uses features which were added in newer versions: * 0.50.0: {'install arg in configure_file'} </quote> Additionally the config file has been renamed to "fuse_config.h" to avoid clashes - 'config.h' is not very specific.
2023-01-13Released 3.13.0Nikolaus Rath-1/+1
2023-01-06adding comments and capability discovery, enum for flags moved to top of fileHereThereBeDragons-0/+16
2022-09-04fuse-loop/fuse_do_work: Avoid lots of thread creations/destructionsBernd Schubert-2/+8
On benchmarking metadata operations with a single threaded bonnie++ and "max_idle_threads" limited to 1, 'top' was showing suspicious 160% cpu usage. Profiling the system with flame graphs showed that an astonishing amount of CPU time was spent in thread creation and destruction. After verifying the code it turned out that fuse_do_work() was creating a new thread every time all existing idle threads were already busy. And then just a few lines later after processing the current request it noticed that it had created too many threads and destructed the current thread. I.e. there was a thread creation/destruction ping-pong. Code is changed to only create new threads if the max number of threads is not reached. Furthermore, thread destruction is disabled, as creation/destruction is expensive in general. With this change cpu usage of passthrough_hp went from ~160% to ~80% (with different values of max_idle_threads). And bonnie values got approximately faster by 90%. This is a with single threaded bonnie++ bonnie++ -x 4 -q -s0 -d <path> -n 30:1:1:10 -r 0 Without this patch, using the default max_idle_threads=10 and just a single bonnie++ the thread creation/destruction code path is not triggered. Just one libfuse and one application thread is just a corner case - the requirement for the issue was just n-application-threads >= max_idle_threads. Signed-off-by: Bernd Schubert <bschubert@ddn.com>
2022-09-04API update for fuse_loop_config additionsBernd Schubert-1/+44
struct fuse_loop_config was passed as a plain struct, without any version identifer. This had two implications 1) Any addition of new parameters required a FUSE_SYMVER for fuse_session_loop_mt() and fuse_loop_mt() as otherwise a read beyond end-of previous struct size might have happened. 2) Filesystems also might have been recompiled and the developer might not have noticed the struct extensions and unexpected for the developer (or people recomliling the code) uninitialized parameters would have been passed. Code is updated to have struct fuse_loop_config as an opaque/private data type for file systems that want version 312 (FUSE_MAKE_VERSION(3, 12)). The deprecated fuse_loop_config_v1 is visible, but should not be used outside of internal conversion functions File systems that want version >= 32 < 312 get the previous struct (through ifdefs) and the #define of fuse_loop_mt and fuse_session_loop_mt ensures that these recompiled file systems call into the previous API, which then converts the struct. This is similar to existing compiled applications when just libfuse updated, but binaries it is solved with the FUSE_SYMVER ABI compact declarations. Signed-off-by: Bernd Schubert <bschubert@ddn.com>
2022-05-02Released 3.11.0Nikolaus Rath-1/+1
2022-01-03Add support for FOPEN_NOFLUSH flagAmir Goldstein-1/+5
Allow requesting from kernel to avoid flush on close at file open time. If kernel does not support FOPEN_NOFLUSH flag, the request will be ignored. For passthrough_hp example, request to avoid flush on close when writeback cache is disabled and file is opened O_RDONLY. Signed-off-by: Amir Goldstein <amir73il@gmail.com>
2020-10-09Released 3.10.0Nikolaus Rath-2/+2
2020-09-20Allow caching symlinks in kernel page cache. (#551)Etienne Dublé-0/+13
This commit defines a new capability called `FUSE_CAP_CACHE_SYMLINKS`. It is off by default but you can now enable it by setting this flag in in the `want` field of the `fuse_conn_info` structure. When enabled, the kernel will save symlinks in its page cache, by making use of the feature introduced in kernel 4.20: https://github.com/torvalds/linux/commit/5571f1e65486be025f73fa6aa30fb03725d362a2
2020-01-27Remove trailing comma in enums (#494)zsugabubus-2/+2
They are illegal in C89/90.
2019-12-31Bump FUSE_MINOR_VERSIONNikolaus Rath-1/+1
This was forgotten over several releases.
2019-11-27Added support for FUSE_EXPLICIT_INVAL_DATA to enable (#474)Albert Chen-0/+23
2019-09-04Introduce callback for loggingStefan Hajnoczi-0/+1
Introduce an API for custom log handler functions. This allows libfuse applications to send messages to syslog(3) or other logging systems. See include/fuse_log.h for details. Convert libfuse from fprintf(stderr, ...) to log_fuse(level, ...). Most messages are error messages with FUSE_LOG_ERR log level. There are also some debug messages which now use the FUSE_LOG_DEBUG log level. Note that lib/mount_util.c is used by both libfuse and fusermount3. Since fusermount3 does not link against libfuse, we cannot call fuse_log() from lib/mount_util.c. This file will continue to use fprintf(stderr, ...) until someone figures out how to split it up. Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2019-08-23Shorten comment.Nikolaus Rath-5/+0
2019-08-23Improve description of READDIRPLUS_AUTO.Nikolaus Rath-0/+9
2019-08-23Clarify bitfield padding issue (#445)AsumFace-2/+8
* Clarify bitfield padding issue * Add a more elaborate note to fuse_file_info
2019-04-16Add documentation for opting out of opendir and releasedir (#391)Chad Austin-0/+12
2019-04-06Add support for in-kernel readdir caching.Nikolaus Rath-5/+13
Fixes: #394.
2019-04-06Various documentation improvementsAlan Somers-5/+16
See issue #389 for some related discussions.
2018-09-20Don't enable adaptive readdirplus unless fs has readdir() handler.Nikolaus Rath-4/+15
2017-11-27Spelling (#223)Josh Soref-2/+2
Fix spelling errors
2017-08-24Add idle_threads mount option.Joseph Dodge-1/+23
2017-07-08Added public fuse_lib_help(), bumped minor versionNikolaus Rath-1/+1
2017-07-08Fixed description of struct fuse_conn_info->time_granNikolaus Rath-2/+3
At least on Linux kernel 4.9, a value of zero gives more than 1-sec accuracy.
2017-06-08Clarify *_timeout semanticsNikolaus Rath-2/+2
When changes always come through kernel, timeouts should be large.
2017-03-15open(): fix documentation of O_TRUNC flagNikolaus Rath-1/+3
The FUSE_CAP_ATOMIC_IO_TRUNC capability is enabled by default, but we didn't update the open() documentation accordingly.
2016-11-29Return signal value if session loop is terminated by signal and improve ↵Nikolaus Rath-2/+2
documentation
2016-11-29Improve documentation of `fuse_file_info.keep_cache`Nikolaus Rath-2/+3
2016-11-22Document that FUSE_CAP_POSIX_ACL turns on -o default_permissionsNikolaus Rath-1/+5
2016-11-22Add support for FUSE_HANDLE_KILLPRIVNikolaus Rath-0/+9
Fixes #116.
2016-11-22Add support for FUSE_POSIX_ACLNikolaus Rath-0/+15
Fixes #117.
2016-11-22Added support for FUSE_PARALLEL_DIROPSNikolaus Rath-0/+10
Enabled by default since we haven't released libfuse 3.0 yet :-). Fixes #112.
2016-11-22Document fuse_conn_info.max_backgroundNikolaus Rath-4/+26
Fixes #95.
2016-11-16Enable more capabilities by default, and document defaults.Nikolaus Rath-7/+42
Fixes #112.
2016-11-16Document "congestion_threshold" parameter.Nikolaus Rath-4/+6
Fixes #96. Thanks to Maxim Patlasov <mpatlasov@virtuozzo.com> for help!
2016-11-14Make max_background and congestion_threshold "officially undocumented"Nikolaus Rath-3/+8
2016-11-14Improve documentation of FUSE_CAP_AUTO_INVAL_DATANikolaus Rath-2/+16
Fixes #84.
2016-11-14Improve description of FUSE_CAP_NO_OPEN_SUPPORT flag.Nikolaus Rath-1/+9
Fixes #107.
2016-11-10Added documentation for FUSE_CAP_FLOCK_LOCKSNikolaus Rath-2/+6
Fixes #106.
2016-11-10Improve documentation of fuse_conn_info.time_gran.Nikolaus Rath-3/+12
Fixes #97.
2016-10-28Clean-up doxygen documentationNikolaus Rath-3/+2
Fixes: #81.
2016-10-27Add max_read to fuse_conn_infoNikolaus Rath-0/+14
Eventually, this setting should be negotiated in the filesystem's init() handler (like e.g. max_write). However, this requires corresponding changes in the FUSE kernel module. In preparation for this (and to allow a transition period) we already allow (and require) filesystems to set the value in the init() handler in addition to the mount option. The end-goal is tracked in issue #91.
2016-10-27Removed some more "Changed in version x.py" comments.Nikolaus Rath-2/+0
2016-10-27Improve documentation of capability flags.Nikolaus Rath-18/+83
2016-10-20Removed all "Introduced in..." commentsNikolaus Rath-9/+6
Since FUSE 3 is breaking backwards compatibility, this really does not matter.
2016-10-15Unify handling of fuse_conn_info optionsNikolaus Rath-0/+55
Instead of using command line options to modify struct fuse_conn_info before and after calling the init() handler, we now give the file system explicit control over this.
2016-10-13do_init(): treat command line options consistentlyNikolaus Rath-2/+5
Previously, some command line options would change the FUSE defaults but leave the final value to the file systems `init` handler while others would override any changes made by `init`. Now, command line options do both: they modify the default, *and* take precedence.
2016-10-10Removed 'async_read' field in fuse_conn_infoNikolaus Rath-5/+0
This is redundant with the capability flags in `wants` and `capable`.
2016-10-08Removed ``-o big_writes`` optionNikolaus Rath-2/+2
This option is obsolete and should always be enabled. File systems that want to limit the size of write requests should use the ``-o max_write=<N>`` option instead.
2016-10-02Don't handle --help and --version in fuse_session_new().Nikolaus Rath-28/+0
Help and version messages can be generated using the new fuse_lowlevel_help(), fuse_lowlevel_version(), fuse_mount_help(), and fuse_mount_version() functions. The fuse_parse_cmdline() function has been made more powerful to do this automatically, and is now explicitly intended only for low-level API users. This is a code simplication patch. We don't have to parse for --help and --version in quite as many places, and we no longer have a low-level initialization function be responsible for the (super-high level) task of printing a program usage message. In the high-level API, we can now handle the command line parsing earlier and avoid running other initialization code if we're just going to abort later on.
generated by cgit v1.2.3 (git 2.39.1) at 2025-10-18 15:16:56 +0000