From: Tejun Heo <tj@kernel.org>
To: Ashish Sangwan <ashishsangwan2@gmail.com>
Cc: Jakob Unterwurzacher <jakobunt@gmail.com>,
Miklos Szeredi <miklos@szeredi.hu>,
fuse-devel <fuse-devel@lists.sourceforge.net>,
Linux-Fsdevel <linux-fsdevel@vger.kernel.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [fuse-devel] Horrible mmap write performance (kernel writeback issue?)
Date: Tue, 12 Apr 2016 07:09:03 -0400 [thread overview]
Message-ID: <20160412110903.GR24661@htj.duckdns.org> (raw)
In-Reply-To: <CAOiN93mbh_rZqAu2uU8MBtgW9iBS2hGBFZrmJA6NJhpXpdea-g@mail.gmail.com>
Hello,
On Tue, Apr 12, 2016 at 02:54:08PM +0530, Ashish Sangwan wrote:
> On Tue, Apr 12, 2016 at 5:54 AM, Tejun Heo <tj@kernel.org> wrote:
> > Hello,
> >
> > On Mon, Apr 11, 2016 at 10:04:42AM +0200, Jakob Unterwurzacher wrote:
> >> What seems to be happening in the kernel is that the estimated device bandwith
> >> drops to zero. I'm not even sure how this works for FUSE, but that's what I
> >> gathered from some printk debugging.
> >
> > Yeah, writeback bw getting messed up is the most likely cause. Prolly
> > some silly bug. I can reproduce the problem. Looking into it.
>
> Probably you want to look into:
> https://lkml.org/lkml/2016/3/10/21
>
> The patch mentioned above solves the issue for me.
Heh, I tracked it down to wb_over_bg_thresh() and fell asleep. Yeah,
that is the right fix.
Thanks.
--
tejun
next prev parent reply other threads:[~2016-04-12 11:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPv9Zmm7WOQvMTTJjvxgXfRXzF7nes5zmJvnAo7GKqY7muWwhA@mail.gmail.com>
[not found] ` <CAPv9ZmkXnzkTAv+60GzVizjB9mrc_LwdSQ7-iimEFpeoV0Opug@mail.gmail.com>
[not found] ` <56E7C009.3070008@gmail.com>
2016-03-16 9:44 ` [fuse-devel] Horrible mmap write performance (kernel writeback issue?) Miklos Szeredi
2016-03-26 21:42 ` Jakob Unterwurzacher
2016-03-28 19:45 ` Miklos Szeredi
2016-03-30 18:47 ` Tejun Heo
[not found] ` <20160330184732.GO7822-qYNAdHglDFBN0TnZuCh8vA@public.gmane.org>
2016-03-31 16:58 ` Antonio SJ Musumeci
2016-04-02 6:34 ` [fuse-devel] " Sedat Dilek
2016-04-11 8:04 ` Jakob Unterwurzacher
2016-04-12 0:24 ` Tejun Heo
2016-04-12 9:24 ` Ashish Sangwan
2016-04-12 11:09 ` Tejun Heo [this message]
2016-04-13 7:20 ` Sedat Dilek
2016-04-18 21:06 ` Jakob Unterwurzacher
2016-04-20 1:35 ` Howard Cochran
2016-04-25 8:07 ` Sedat Dilek
2016-05-02 9:39 ` Sedat Dilek
[not found] ` <CA+icZUXjBim3cNhTLK3V0ko_iRsYAKV9Nhavg4pm24bNKTnp-A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-05-10 22:55 ` Jakob Unterwurzacher
2016-05-11 7:07 ` [fuse-devel] " Sedat Dilek
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=20160412110903.GR24661@htj.duckdns.org \
--to=tj@kernel.org \
--cc=ashishsangwan2@gmail.com \
--cc=fuse-devel@lists.sourceforge.net \
--cc=jakobunt@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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).