diff options
| author |  Nikolaus Rath <Nikolaus@rath.org> | 2016-10-27 21:38:42 -0700 |
|---|---|---|
| committer | Nikolaus Rath <Nikolaus@rath.org> | 2016-10-27 21:38:42 -0700 |
| commit | e885e84f796da2433907e57358bc4916bca30a50 (patch) | |
| tree | 278350db190c3f8f50933397d368cc9fbbbe74e9 /doc | |
| parent | 4fade0c616a9227e42043ac3332f0fc59a6df327 (diff) | |
Add max_read to fuse_conn_info
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.
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/mount.fuse.8 | 8 |
1 files changed, 7 insertions, 1 deletions
diff --git a/doc/mount.fuse.8 b/doc/mount.fuse.8 index ada4b07..bc4b2fa 100644 --- a/doc/mount.fuse.8 +++ b/doc/mount.fuse.8 @@ -100,11 +100,17 @@ the filesystem owner but set internally by the filesystem. \fBmax_read=N\fP With this option the maximum size of read operations can be set. The default is infinite, but typically the kernel enforces its own limit -in addition to this one. +in addition to this one. A value of zero corresponds to no limit. This option should not be specified by the filesystem owner. The correct (or optimum) value depends on the filesystem implementation and should thus be set by the filesystem internally. + +This mount option is deprecated in favor of direct negotiation over +the device fd (as done for e.g. the maximum size of write +operations). For the time being, libfuse-using filesystems that want +to limit the read size must therefore use this mount option \fIand\fP +set the same value again in the init() handler. .TP \fBfd=N\fP The file descriptor to use for communication between the userspace |