From e885e84f796da2433907e57358bc4916bca30a50 Mon Sep 17 00:00:00 2001 From: Nikolaus Rath Date: Thu, 27 Oct 2016 21:38:42 -0700 Subject: 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. --- ChangeLog.rst | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'ChangeLog.rst') 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=`` 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. -- cgit v1.2.3