From: Constantine Shulyupin <const@MakeLinux.com>
To: miklos@szeredi.hu, viro@zeniv.linux.org.uk, corbet@lwn.net,
liushuoran@jd.com, mitsuo.hayasaka.hu@hitachi.com,
linux-fsdevel@vger.kernel.org (open list:FUSE: FILESYSTEM IN
USERSPACE), linux-doc@vger.kernel.org (open list:DOCUMENTATION),
linux-kernel@vger.kernel.org (open list)
Cc: amir73il@gmail.com, Constantine Shulyupin <const@MakeLinux.com>
Subject: [PATCH v3 2/3] fuse: add max_pages option
Date: Wed, 15 Aug 2018 00:17:15 +0300 [thread overview]
Message-ID: <20180814211717.22170-2-const@MakeLinux.com> (raw)
In-Reply-To: <20180814211717.22170-1-const@MakeLinux.com>
Signed-off-by: Constantine Shulyupin <const@MakeLinux.com>
---
Documentation/filesystems/fuse.txt | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/Documentation/filesystems/fuse.txt b/Documentation/filesystems/fuse.txt
index 13af4a49e7db..d4e832fe9ce6 100644
--- a/Documentation/filesystems/fuse.txt
+++ b/Documentation/filesystems/fuse.txt
@@ -108,7 +108,10 @@ 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 anyway to max_pages (which by default is 32 or 128KB on x86).
+
+'max_pages=N'
+ Maximal number of pages per request. The default is 32 or 128KB on x86.
'blksize=N'
--
2.17.1
next prev parent reply other threads:[~2018-08-15 0:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 21:17 [PATCH v3 1/3] fuse: add max_pages option Constantine Shulyupin
2018-08-14 21:17 ` Constantine Shulyupin [this message]
2018-08-14 21:17 ` [PATCH v3 3/3] fuse: export pipe_max_size for max_pages Constantine Shulyupin
2018-08-15 7:56 ` [PATCH v3 1/3] fuse: add max_pages option Miklos Szeredi
2018-08-15 9:21 ` kbuild test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180814211717.22170-2-const@MakeLinux.com \
--to=const@makelinux.com \
--cc=amir73il@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liushuoran@jd.com \
--cc=miklos@szeredi.hu \
--cc=mitsuo.hayasaka.hu@hitachi.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).