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 /ChangeLog.rst | |
| 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 'ChangeLog.rst')
| -rw-r--r-- | ChangeLog.rst | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/ChangeLog.rst b/ChangeLog.rst index 2019325..65df8a5 100644 --- a/ChangeLog.rst +++ b/ChangeLog.rst @@ -1,6 +1,12 @@ Unreleased Changes ================== +* Added a `max_read` field to `struct fuse_conn_info`. For the time + being, the maximum size of read requests has to be specified both + there *and* passed to fuse_session_new() using the ``-o + max_read=<n>`` mount option. At some point in the future, specifying + the mount option will no longer be necessary. + * Documentation: clarified that the fuse_argv structure that is passed to `fuse_new()` and `fuse_lowlevel_new()` must always contain at least one element. |