From f1518cd0845a69b09bd9254120d4334ef2a01614 Mon Sep 17 00:00:00 2001 From: Martin Pärtel Date: Tue, 12 Jul 2022 21:26:25 +0300 Subject: Reverted change in 1.16.0 that made direct_io the default. Fixes #117 --- src/bindfs.1 | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) (limited to 'src/bindfs.1') diff --git a/src/bindfs.1 b/src/bindfs.1 index 7cb13d0..3c2f92b 100644 --- a/src/bindfs.1 +++ b/src/bindfs.1 @@ -409,13 +409,18 @@ Run bindfs in multithreaded mode. While bindfs is designed to be otherwise thread-safe, there is currently a race condition that may pose a security risk for some use cases. See \fB\%BUGS\fP below. +.TP +.B \-\-direct\-io, \-o direct\-io + +Forwards each read/write operation 1:1 to the underlying FS, +disabling batching and caching by the kernel. Some applications may +require this, however it may be incompatible with other applications, +as currently it has issues with \fBmmap\fP(2) calls, at least. + .TP .B \-\-no\-direct\-io, \-o no\-direct\-io -By default, each read/write operation is forwarded 1:1 to the underlying FS, -disabling batching and caching by the kernel. Specify this option for default -FUSE behaviour, which may be more performant with some applications but -incompatible with others. +This option is provided in case the default changes in the future. .TP .B \-\-forward\-odirect=\fIalignment\fP, \-o forward\-odirect=\fIalignment\fP -- cgit v1.2.3