linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Constantine Shulyupin <const@makelinux.com>
To: "Miklos Szeredi" <miklos@szeredi.hu>,
	"open list:FUSE: FILESYSTEM IN USERSPACE"
	<linux-fsdevel@vger.kernel.org>,
	"Jonathan Corbet" <corbet@lwn.net>, 刘硕然 <liushuoran@jd.com>,
	mitsuo.hayasaka.hu@hitachi.com
Cc: Amir Goldstein <amir73il@gmail.com>
Subject: Re: [PATCH v4] fuse: add max_pages option
Date: Wed, 26 Sep 2018 11:54:44 +0300	[thread overview]
Message-ID: <CAE7jHC_+NkmqUQx937v4eWwOjDALzxStW3L1t3YUxhMKmtWjBg@mail.gmail.com> (raw)
In-Reply-To: <20180906123706.28691-1-const@MakeLinux.com>

Hi Miklos,

Passed 20 days since the previous messages, so would you like to
review the patch?
I've added reproduction and measurement details up your request.
Also this patch can help resolve BDI_CAP_STRICTLIMIT performance issue
reported recently by liushuoran@jd.com.

Thanks

On Thu, Sep 6, 2018 at 3:37 PM Constantine Shulyupin
<const@makelinux.com> wrote:
>
> Replace FUSE_MAX_PAGES_PER_REQ with the configurable
> mount parameter max_pages to improve performance.

Link to message: https://marc.info/?l=linux-fsdevel&m=153623932516084&w=2

  reply	other threads:[~2018-09-26 15:06 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 [this message]
2018-09-26  9:19   ` Miklos Szeredi
2018-09-26  9:39     ` 答复: " 刘硕然
2018-09-26 10:06       ` Constantine Shulyupin
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_+NkmqUQx937v4eWwOjDALzxStW3L1t3YUxhMKmtWjBg@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).