Add an explanation about the sysfs parameter to limit the maximum read/write request size.
Signed-off-by: Mitsuo Hayasaka <[email protected]> Cc: Rob Landley <[email protected]> Cc: Miklos Szeredi <[email protected]> Cc: Nikolaus Rath <[email protected]> Cc: Liu Yuan <[email protected]> Cc: Has-Wen Nienhuys <[email protected]> --- Documentation/filesystems/fuse.txt | 15 ++++++++++++++- 1 files changed, 14 insertions(+), 1 deletions(-) diff --git a/Documentation/filesystems/fuse.txt b/Documentation/filesystems/fuse.txt index 13af4a4..4e706ec 100644 --- a/Documentation/filesystems/fuse.txt +++ b/Documentation/filesystems/fuse.txt @@ -108,13 +108,26 @@ Mount options With this option the maximum size of read operations can be set. The default is infinite. Note that the size of read requests is - limited anyway to 32 pages (which is 128kbyte on i386). + limited by max_pages_per_req sysfs parameter (See below for details.) 'blksize=N' Set the block size for the filesystem. The default is 512. This option is only valid for 'fuseblk' type mounts. +Sysfs parameter +~~~~~~~~~~~~~~~ + + '/sys/fs/fuse/max_pages_per_req' + +Specify max request size in pages, which limits max_read/max_write +mount option. The default is 32 pages (which is 128kbyte on i386). +It can be changed to arbitrary number between 32 and the number of +pages equivalent to pipe_max_size. + +Changing it may improve read/write throughput on systems. Existing +FUSE mount must be remounted for this change to take effect. + Control filesystem ~~~~~~~~~~~~~~~~~~ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
