From: Constantine Shulyupin <const@makelinux.com>
To: 刘硕然 <liushuoran@jd.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
"open list:FUSE: FILESYSTEM IN USERSPACE"
<linux-fsdevel@vger.kernel.org>, Jonathan Corbet <corbet@lwn.net>,
mitsuo.hayasaka.hu@hitachi.com,
Amir Goldstein <amir73il@gmail.com>
Subject: Re: [PATCH v4] fuse: add max_pages option
Date: Wed, 26 Sep 2018 13:06:56 +0300 [thread overview]
Message-ID: <CAE7jHC-gYyH--H_FMkZM8=UoEMS+RkzwUF15DvuAdrMnFBWM+Q@mail.gmail.com> (raw)
In-Reply-To: <ef5fb36737924682b34277f80203300f@jd.com>
Hi Shuoran,
On Wed, Sep 26, 2018 at 12:40 PM 刘硕然 <liushuoran@jd.com> wrote:
> I haven't tested the patch yet. But after reviewing the patch, I don't see anything related to BDI_CAP_STRICTLIMIT. So would you please explain a little bit more? Thanks.
Bigger size of request reduces total number of requests and reduces
overhead of per request operations.
> PS: I did try increasing FUSE_MAX_PAGES_PER_REQ, but it seemed not helping in my scenario(writeback cache enabled, 4K writes, total write size is not very large).
To utilize FUSE_MAX_PAGES_PER_REQ in kernel it is must to increase
KERNEL_BUF_PAGES it libfuse too. I have libfuse patch with
configurable max_pages.
But 4K writes will not benefit from increase of request size, which
now is 128K and proposed size is 1M.
Thanks
next prev parent reply other threads:[~2018-09-26 16:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-06 12:37 [PATCH v4] fuse: add max_pages option Constantine Shulyupin
2018-09-26 8:54 ` Constantine Shulyupin
2018-09-26 9:19 ` Miklos Szeredi
2018-09-26 9:39 ` 答复: " 刘硕然
2018-09-26 10:06 ` Constantine Shulyupin [this message]
2018-09-26 10:39 ` 刘硕然
2018-10-01 9:18 ` Miklos Szeredi
2018-10-01 9:16 ` Miklos Szeredi
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='CAE7jHC-gYyH--H_FMkZM8=UoEMS+RkzwUF15DvuAdrMnFBWM+Q@mail.gmail.com' \
--to=const@makelinux.com \
--cc=amir73il@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=liushuoran@jd.com \
--cc=miklos@szeredi.hu \
--cc=mitsuo.hayasaka.hu@hitachi.com \
/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).