From: Miklos Szeredi <miklos@szeredi.hu>
To: 刘硕然 <liushuoran@jd.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: FUSE: write operations trigger balance_dirty_pages when using writeback cache
Date: Thu, 9 Aug 2018 10:30:22 +0200 [thread overview]
Message-ID: <CAJfpegscozvNV3R4h1NZCGLq_Te8AHXEAxymRJNj96OkmPFFJw@mail.gmail.com> (raw)
In-Reply-To: <EA52CBCF76D5E04D95BED55B83577BE7A67744@MBX50.360buyAD.local>
On Thu, Aug 9, 2018 at 9:31 AM, 刘硕然 <liushuoran@jd.com> wrote:
> Thank you for the prompt reply.
>
> I tried this config, but still can get balance_dirty_pages triggered.
I think it may be due to BDI_CAP_STRICTLIMIT used by fuse. If you
remove that setting from fuse in the kernel you should not be getting
the balance_dirty_pages() as often.
Not sure if that's the realproblem, though, that depends on how much
time is spent in balance_dirty_pages(). You can try profiling the
kernel to find that out.
My guess is that the real cause of the slowdown is some other place.
There's for example a known issue with selinux related getxattr
thrashing. Disabling getxattr on your filesystem may significantly
improve performance.
Thanks,
Miklos
next prev parent reply other threads:[~2018-08-09 10:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-09 7:31 FUSE: write operations trigger balance_dirty_pages when using writeback cache 刘硕然
2018-08-09 8:30 ` Miklos Szeredi [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-08-09 12:08 刘硕然
2018-08-09 12:25 ` Miklos Szeredi
2018-08-09 3:37 刘硕然
2018-08-09 7:14 ` 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=CAJfpegscozvNV3R4h1NZCGLq_Te8AHXEAxymRJNj96OkmPFFJw@mail.gmail.com \
--to=miklos@szeredi.hu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liushuoran@jd.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).