Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
IronPort-SDR: zWzZHVQv8KAvfcj9g87f9+LUVHJVdDmzt3cAL0xKVF7APzx2uXtJAifMVnG233PY4+axoYYuaV
 jeRP8wFZ58B0H8BHnVPbtmfDV7LQ80KCxk5+A3TYoIv/2FVv+ZlOw3Szcxg2lLBEWXOnLmyifG
 5LqL3vwfrcpplNYsBDaGaxq17JKHCMvKQB71RV5ZqEMSQQRZD2NWjeqY7bCxg9iQ6Ff000W2kN
 xAgIKPo39w1ISWqHXw8ZLudI1KPvqVN7+gxYRS7tMTBn/R+3FyYnDJKRUEdYKhFc7TW640DQUp
 nj8=
IronPort-SDR: gsmis9QN3KT0tmYYyC5VBBVqpxBmi0TPXKAD9Xu8MoY7mN9XctIigbMa+iFkE8cTFg9XbP2gPw
 vqN0Ib1AXXqwYUFV7qSrPVjYmXP4+WlheHDoa49BA02cVtAjhDt6QClHNGymv3PkPJdj4eFdbB
 mhkcJH9Roylj2Cz5AMt+RuNwFXpX0YuQdNXr6ib5vPSu0ry0NcKE26nrwbDJ7kfTVF6wuywtxT
 rKgkmX4OljOYEf8bl6aAaVROBX5BrKhKM6frQvwtD2WNuzJ7ROSM6TGXqUu0BPggp8urT9Fmkw
 4FM=
WDCIronportException: Internal
Message-ID: <f23d1a4a-cdf9-3ab3-d2ec-fe55f5d06915@opensource.wdc.com>
Date:   Mon, 21 Nov 2022 09:20:03 +0900
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.5.0
Subject: Re: [PATCH V6 2/8] block, bfq: forbid stable merging of queues
 associated with different actuators
Content-Language: en-US
To:     Paolo Valente <paolo.valente@linaro.org>,
        Jens Axboe <axboe@kernel.dk>
Cc:     linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
        arie.vanderhoeven@seagate.com, rory.c.chen@seagate.com
References: <20221103162623.10286-1-paolo.valente@linaro.org>
 <20221103162623.10286-3-paolo.valente@linaro.org>
From:   Damien Le Moal <damien.lemoal@opensource.wdc.com>
Organization: Western Digital Research
In-Reply-To: <20221103162623.10286-3-paolo.valente@linaro.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 11/4/22 01:26, Paolo Valente wrote:
> If queues associated with different actuators are merged, then control
> is lost on each actuator. Therefore some actuator may be
> underutilized, and throughput may decrease. This problem cannot occur
> with basic queue merging, because the latter is triggered by spatial
> locality, and sectors for different actuators are not close to each
> other. Yet it may happen with stable merging. To address this issue,
> this commit prevents stable merging from occurring among queues
> associated with different actuators.
> 
> Signed-off-by: Paolo Valente <paolo.valente@linaro.org>
> ---
>  block/bfq-iosched.c | 13 +++++++++----
>  1 file changed, 9 insertions(+), 4 deletions(-)
> 
> diff --git a/block/bfq-iosched.c b/block/bfq-iosched.c
> index 5c69394bbb65..ec4b0e70265f 100644
> --- a/block/bfq-iosched.c
> +++ b/block/bfq-iosched.c
> @@ -5705,9 +5705,13 @@ static struct bfq_queue *bfq_do_or_sched_stable_merge(struct bfq_data *bfqd,
>  	 * it has been set already, but too long ago, then move it
>  	 * forward to bfqq. Finally, move also if bfqq belongs to a
>  	 * different group than last_bfqq_created, or if bfqq has a
> -	 * different ioprio or ioprio_class. If none of these
> -	 * conditions holds true, then try an early stable merge or
> -	 * schedule a delayed stable merge.
> +	 * different ioprio, ioprio_class or actuator_idx. If none of
> +	 * these conditions holds true, then try an early stable merge
> +	 * or schedule a delayed stable merge. As for the condition on
> +	 * actuator_idx, the reason is that, if queues associated with
> +	 * different actuators are merged, then control is lost on
> +	 * each actuator. Therefore some actuator may be
> +	 * underutilized, and throughput may decrease.
>  	 *
>  	 * A delayed merge is scheduled (instead of performing an
>  	 * early merge), in case bfqq might soon prove to be more
> @@ -5725,7 +5729,8 @@ static struct bfq_queue *bfq_do_or_sched_stable_merge(struct bfq_data *bfqd,
>  			bfqq->creation_time) ||
>  		bfqq->entity.parent != last_bfqq_created->entity.parent ||
>  		bfqq->ioprio != last_bfqq_created->ioprio ||
> -		bfqq->ioprio_class != last_bfqq_created->ioprio_class)
> +		bfqq->ioprio_class != last_bfqq_created->ioprio_class ||
> +		bfqq->actuator_idx != last_bfqq_created->actuator_idx)
>  		*source_bfqq = bfqq;
>  	else if (time_after_eq(last_bfqq_created->creation_time +
>  				 bfqd->bfq_burst_interval,

Reviewed-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>

-- 
Damien Le Moal
Western Digital Research