From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <efault@gmx.de>
Message-ID: <1504200711.666.27.camel@gmx.de>
Subject: Re: [PATCH BUGFIX/IMPROVEMENT V2 0/3] three bfq fixes restoring
 service guarantees with random sync writes in bg
From: Mike Galbraith <efault@gmx.de>
To: Paolo Valente <paolo.valente@linaro.org>
Cc: Mel Gorman <mgorman@techsingularity.net>, Jens Axboe <axboe@kernel.dk>,
 linux-block <linux-block@vger.kernel.org>, Linux Kernel Mailing List
 <linux-kernel@vger.kernel.org>,  Ulf Hansson <ulf.hansson@linaro.org>,
 broonie@kernel.org, lee.tibbert@gmail.com, oleksandr@natalenko.name
Date: Thu, 31 Aug 2017 19:31:51 +0200
In-Reply-To: <970115C1-6336-458D-BBD5-3E5054C4553D@linaro.org>
References: <20170831064631.2223-1-paolo.valente@linaro.org>
	 <20170831144257.oa5nm6vzihpam6kw@techsingularity.net>
	 <1504199166.666.11.camel@gmx.de>
	 <970115C1-6336-458D-BBD5-3E5054C4553D@linaro.org>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
List-ID: <linux-block@vger.kernel.org>

On Thu, 2017-08-31 at 19:12 +0200, Paolo Valente wrote:
> > Il giorno 31 ago 2017, alle ore 19:06, Mike Galbraith <efault@gmx.de> h=
a scritto:
> >=20
> > On Thu, 2017-08-31 at 15:42 +0100, Mel Gorman wrote:
> >> On Thu, Aug 31, 2017 at 08:46:28AM +0200, Paolo Valente wrote:
> >>> [SECOND TAKE, with just the name of one of the tester fixed]
> >>>=20
> >>> Hi,
> >>> while testing the read-write unfairness issues reported by Mel, I
> >>> found BFQ failing to guarantee good responsiveness against heavy
> >>> random sync writes in the background, i.e., multiple writers doing
> >>> random writes and systematic fdatasync [1]. The failure was caused by
> >>> three related bugs, because of which BFQ failed to guarantee to
> >>> high-weight processes the expected fraction of the throughput.
> >>>=20
> >>=20
> >> Queued on top of Ming's most recent series even though that's still a =
work
> >> in progress. I should know in a few days how things stand.
> >=20
> > It seems to have cured an interactivity issue I regularly meet during
> > kbuild final link/depmod phase of fat kernel kbuild, especially bad
> > with evolution mail usage during that on spinning rust.  Can't really
> > say for sure given this is not based on measurement.
> >
>=20
>=20
> Great!  Actually, when I found these bugs, I thought also about the
> issues you told me you experienced with updatedb running.  But then I
> forgot to tell you that these fixes might help.

I'm going to actively test that, because that is every bit as
infuriating as the evolution thing, only updatedb is nukable. =C2=A0In fact=
,
it infuriated me to the point that it no longer has a crontab entry,
runs only when I decide to run it. =C2=A0At this point, I'll be pretty
surprised if that rotten <naughty words> is still alive.

	-Mike

From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752005AbdHaRcD convert rfc822-to-8bit (ORCPT <rfc822;w@1wt.eu>);
        Thu, 31 Aug 2017 13:32:03 -0400
Received: from mout.gmx.net ([212.227.17.22]:59386 "EHLO mout.gmx.net"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1751622AbdHaRcB (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 31 Aug 2017 13:32:01 -0400
Message-ID: <1504200711.666.27.camel@gmx.de>
Subject: Re: [PATCH BUGFIX/IMPROVEMENT V2 0/3] three bfq fixes restoring
 service guarantees with random sync writes in bg
From: Mike Galbraith <efault@gmx.de>
To: Paolo Valente <paolo.valente@linaro.org>
Cc: Mel Gorman <mgorman@techsingularity.net>, Jens Axboe <axboe@kernel.dk>,
        linux-block <linux-block@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Ulf Hansson <ulf.hansson@linaro.org>, broonie@kernel.org,
        lee.tibbert@gmail.com, oleksandr@natalenko.name
Date: Thu, 31 Aug 2017 19:31:51 +0200
In-Reply-To: <970115C1-6336-458D-BBD5-3E5054C4553D@linaro.org>
References: <20170831064631.2223-1-paolo.valente@linaro.org>
         <20170831144257.oa5nm6vzihpam6kw@techsingularity.net>
         <1504199166.666.11.camel@gmx.de>
         <970115C1-6336-458D-BBD5-3E5054C4553D@linaro.org>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.20.5 
Mime-Version: 1.0
Content-Transfer-Encoding: 8BIT
X-Provags-ID: V03:K0:w9uxBP6N8+G17YRAOjU7LjoiV/gzMjZx31vfDU88z0uZO5yikQY
 Cw2+IGv+jZd0pq0g4mpE8Aj/xe/M/3IawXUU7FHpAE77EWJhuSialegUmGujiNUBG3YogEH
 3UWwTTrJ14+lfK2VWFFuXVHZBcRC9g2bs65wRKwaiFgW4mTo+aV8UHHk+ZYXzK7L2oUGGh5
 lcBbDyLW2t8p4DfUX/CAw==
X-UI-Out-Filterresults: notjunk:1;V01:K0:qffd6vGIox8=:nQ2eFqqFJ5bYHuEg8S5KU3
 jST7hPb6ySXkPdDAKhBRWW4aEn2ek0IMrfHjHL2bqOVHUKeEOsA8In6otxWB7KyU1rIjfHr3z
 gzzeBd2Jex9zlkgkM4NyDO8nVUDzf2akixT5EJ/oCnAzo3Zv+YTecpVRtF1g7ealnmX0Dn5ph
 BJJ3dTgof4Fb8Is2s9leOAZmgstFd50M5rji7KqEQ2nqcRnsGu3WiWttjtI48BtaNj4Nzbk4r
 bFzUS7QZLf8PnehKVBIB2VwRUvJiThELD67rscSdUy+gOx8BZFyfZKvhRXzMO8lScnhkSPKYm
 sZRzInQQX/K0dN5/loQGeJuVAK/a6djOR84xVPfVqWgGprW6VIPpFDQWMDbQ2ZEtmRYJUZ9yZ
 frxdKHbz90jGq+ghOlr+5kzy+j9tB/4Jqg+LJNx6nYXAqngnNrUFcCD3VB2E9m2XCwMyzsr/v
 kKgJF4ti/PKK/8f6wF/xI9BBAEhfTgMoJ/ePLBR7XTUKCyFiKk3bbOnd0mNxw47zMOJ8usHN+
 vLVWrNdnUorQVHB5GSR1wh97OboJqktChLOCNDtZFw0elwLcbISrh+6VfgNeN1OjKLu33AWNU
 m/yGkwu/lBlXezkBNIrz56ftqlE1qLWEOdwaSnUk5msOskvabVfZBTip974DvFCzQuWbFCP9r
 E1FuDHlHwQc0/NFO8xefoyzOVEfIBqI9bkPrrKmkgobWB+CJjbyzxyJWdjPpJxUOb1Z2EXmXC
 2dyce/H+UzR9XGdJWudC7uT5bFot61QN3J+CDvJaRaT2+Uqeq5Uj57PXuQ13xxyOz4zKiSVX/
 oo5bQKxepJ+g3m7B690iK5wAuLw3cVaHEK0e+0ThI977/9sIf8=
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Thu, 2017-08-31 at 19:12 +0200, Paolo Valente wrote:
> > Il giorno 31 ago 2017, alle ore 19:06, Mike Galbraith <efault@gmx.de> ha scritto:
> > 
> > On Thu, 2017-08-31 at 15:42 +0100, Mel Gorman wrote:
> >> On Thu, Aug 31, 2017 at 08:46:28AM +0200, Paolo Valente wrote:
> >>> [SECOND TAKE, with just the name of one of the tester fixed]
> >>> 
> >>> Hi,
> >>> while testing the read-write unfairness issues reported by Mel, I
> >>> found BFQ failing to guarantee good responsiveness against heavy
> >>> random sync writes in the background, i.e., multiple writers doing
> >>> random writes and systematic fdatasync [1]. The failure was caused by
> >>> three related bugs, because of which BFQ failed to guarantee to
> >>> high-weight processes the expected fraction of the throughput.
> >>> 
> >> 
> >> Queued on top of Ming's most recent series even though that's still a work
> >> in progress. I should know in a few days how things stand.
> > 
> > It seems to have cured an interactivity issue I regularly meet during
> > kbuild final link/depmod phase of fat kernel kbuild, especially bad
> > with evolution mail usage during that on spinning rust.  Can't really
> > say for sure given this is not based on measurement.
> >
> 
> 
> Great!  Actually, when I found these bugs, I thought also about the
> issues you told me you experienced with updatedb running.  But then I
> forgot to tell you that these fixes might help.

I'm going to actively test that, because that is every bit as
infuriating as the evolution thing, only updatedb is nukable.  In fact,
it infuriated me to the point that it no longer has a crontab entry,
runs only when I decide to run it.  At this point, I'll be pretty
surprised if that rotten <naughty words> is still alive.

	-Mike