linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakob Unterwurzacher <jakobunt@gmail.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: 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: Sat, 26 Mar 2016 22:42:45 +0100	[thread overview]
Message-ID: <56F70255.6070806@gmail.com> (raw)
In-Reply-To: <CAJfpegsw8J6TNmT_WvT6ihgFfcWpe748D9Ki5Wna8ukKwnCtWw@mail.gmail.com>

On 16.03.2016 10:44, Miklos Szeredi wrote:
> On Tue, Mar 15, 2016 at 8:55 AM, Jakob Unterwurzacher
> <jakobunt@gmail.com> wrote:
>> Just for anybody finding this thread: This still happens in v4.4, it
>> just took longer to trigger.
>>
>> I have posted more details to linux-kernel (copy-pasted below),
>> http://thread.gmane.org/gmane.linux.kernel/2132944
> 
> Okay, so you can reproduce this relatively quickly.   Can you try "git
> bisect" to find exactly which commit is responsible?
> 
> Thanks,
> Miklos

That took a while, but it looks like it got it:

> commit 947e9762a8ddefda38aa21e249e6a4fec215cd12
> Author: Tejun Heo <tj@kernel.org>
> Date:   Fri May 22 18:23:32 2015 -0400
> 
>     writeback: update wb_over_bg_thresh() to use wb_domain aware operations

Note that this commens seems to only activate changes that happened in the
commit before, aa661bb:

> commit aa661bbe1e61ce80ca4ae98804f673ede94b0827
> Author: Tejun Heo <tj@kernel.org>
> Date:   Fri May 22 18:23:31 2015 -0400
> 
>     writeback: move over_bground_thresh() to mm/page-writeback.c


Anyway, I can reliably reboot between aa661bb and 947e976 and always get the
same results:

aa661bb passes
947e976 fails

I you want to reproduce, clone https://github.com/rfjakob/mmapwrite.git and
run ./encfs-test.sh (needs encfs installed). On the bad kernel, it will hang
within a few seconds.

Thanks,
Jakob

  reply	other threads:[~2016-03-26 21:42 UTC|newest]

Thread overview: 15+ 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 [this message]
2016-03-28 19:45         ` Miklos Szeredi
2016-03-30 18:47           ` Tejun Heo
2016-04-02  6:34             ` 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
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]                             ` <CAPv9Zm=F5EzYQsiH=+=gP9a6H40Cqv9usWMXst42-uxB=J7Tww@mail.gmail.com>
2016-05-11  7:07                               ` 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=56F70255.6070806@gmail.com \
    --to=jakobunt@gmail.com \
    --cc=fuse-devel@lists.sourceforge.net \
    --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).