diff options
| author | Peter Keresztes Schmidt <carbenium@outlook.com> | 2019-07-30 22:40:24 +0200 |
|---|---|---|
| committer | Peter Keresztes Schmidt <carbenium@outlook.com> | 2019-08-08 12:22:43 +0200 |
| commit | b4047cdfe316d624e5cb1d83d165d25339775a72 (patch) | |
| tree | fb460048e2c7f97e40f84d274d1c12c672e91688 /client | |
| parent | 422a9a0f41aa5583fba0d2f6a47c8a34bc79b4ab (diff) | |
| download | gvfs-b4047cdfe316d624e5cb1d83d165d25339775a72.tar.gz | |
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.
Diffstat (limited to 'client')
| -rw-r--r-- | client/gvfsfusedaemon.c | 4 |
1 files changed, 0 insertions, 4 deletions
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; } |