From b4047cdfe316d624e5cb1d83d165d25339775a72 Mon Sep 17 00:00:00 2001 From: Peter Keresztes Schmidt Date: Tue, 30 Jul 2019 22:40:24 +0200 Subject: fuse: Remove max_write limit Since we moved to fuse 3 big_writes are enabled by default. There is no need to manually specify max_write anymore since the set value is actually smaller than the libfuse default. Let libfuse figure out the right value. This increses the transfer speed from 31MiB/s to 43MiB/s between my system and a SMB share. --- client/gvfsfusedaemon.c | 4 ---- 1 file changed, 4 deletions(-) (limited to 'client') diff --git a/client/gvfsfusedaemon.c b/client/gvfsfusedaemon.c index 6961d0a1..b0be2f71 100644 --- a/client/gvfsfusedaemon.c +++ b/client/gvfsfusedaemon.c @@ -2491,10 +2491,6 @@ vfs_init (struct fuse_conn_info *conn, struct fuse_config *cfg) /* Prevent out-of-order readahead */ conn->want &= ~FUSE_CAP_ASYNC_READ; - /* Use up to a 64KiB write block size. Only has an effect if -o big_writes - * is given on the command-line. */ - conn->max_write = 65536; - return NULL; } -- cgit v1.2.1