archive mirror
 help / color / mirror / Atom feed
From: 刘硕然 <>
To: Miklos Szeredi <>,
	Constantine Shulyupin <>
	<>, Jonathan Corbet <>,
	"" <>,
	Amir Goldstein <>
Subject: 答复: [PATCH v4] fuse: add max_pages option
Date: Wed, 26 Sep 2018 09:39:56 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Constantine,

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.

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).

Shuoran Liu

发件人: Miklos Szeredi [] 
发送时间: 2018年9月26日 17:20
收件人: Constantine Shulyupin <>
抄送: open list:FUSE: FILESYSTEM IN USERSPACE <>; Jonathan Corbet <>; 刘硕然 <>;; Amir Goldstein <>
主题: Re: [PATCH v4] fuse: add max_pages option

On Wed, Sep 26, 2018 at 10:54 AM, Constantine Shulyupin <> wrote:
> 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

Do you have feedback from <> that this patch helps?


  reply	other threads:[~2018-09-26 15:58 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     ` 刘硕然 [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* 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).