linux-kernel - Re: [fuse-devel] Horrible mmap write performance (kernel writeback issue?)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+icZUX1199rZksFtDeDijvQ6GFpdd6jbO5_QHo2Ui6zsTF98w@mail.gmail.com>
Date:	Mon, 25 Apr 2016 10:07:48 +0200
From:	Sedat Dilek <sedat.dilek@...il.com>
To:	Howard Cochran <hcochran@...nelspring.com>
Cc:	Jakob Unterwurzacher <jakobunt@...il.com>,
	Tejun Heo <tj@...nel.org>,
	Ashish Sangwan <ashishsangwan2@...il.com>,
	Miklos Szeredi <miklos@...redi.hu>,
	fuse-devel <fuse-devel@...ts.sourceforge.net>,
	Linux-Fsdevel <linux-fsdevel@...r.kernel.org>,
	Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [fuse-devel] Horrible mmap write performance (kernel writeback issue?)

On Wed, Apr 20, 2016 at 3:35 AM, Howard Cochran
<hcochran@...nelspring.com> wrote:
> On Mon, Apr 18, 2016 at 5:06 PM, Jakob Unterwurzacher
> <jakobunt@...il.com> wrote:
>> On 12.04.2016 13:09, Tejun Heo wrote:
>>>>
>>>> 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.
>>
>> Works wonderfully now, thanks to everybody involved. Is it too late for 4.6?
>>
>> Best regards,
>> Jakob
>>
> Jakob, et. al.
>
> You're welcome.  That performance problem stumped me for a couple of
> weeks until tracked it down and submitted the fix.
>

What has happened to "writeback: Fix performance regression in
wb_over_bg_thresh()"?
I checked Linux v4.6-rc5, it is not included.
Is it in another Git tree? If yes, where?

- sed@ -