From: Paolo Valente <paolo.valente@linaro.org>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block <linux-block@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Arie van der Hoeven <arie.vanderhoeven@seagate.com>,
Rory Chen <rory.c.chen@seagate.com>,
Federico Gavioli <f.gavioli97@gmail.com>
Subject: Re: [PATCH V6 6/8] block, bfq: retrieve independent access ranges from request queue
Date: Thu, 8 Dec 2022 11:43:34 +0100 [thread overview]
Message-ID: <41604669-2D56-4524-8FA1-527FEAD06B29@linaro.org> (raw)
In-Reply-To: <9eba7529-8879-fbba-4e17-f174ef401513@opensource.wdc.com>
> Il giorno 7 dic 2022, alle ore 00:34, Damien Le Moal <damien.lemoal@opensource.wdc.com> ha scritto:
>
>
[...]
>> Just, let me avoid setting the fields bfqd->sector and
>> bfqd->nr_sectors for a case where we don't use them.
>
> Sure. But if you do not use them thanks to "if (num_actuators == 1)"
> optimizations, it would still not hurt to set these fields. That actually
> could be helpful for debugging.
>
Got it. I'm about to send a V9 that applies this last suggestion of yours.
Thanks,
Paolo
next prev parent reply other threads:[~2022-12-08 10:49 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 16:26 [PATCH V6 0/8] block, bfq: extend bfq to support multi-actuator drives Paolo Valente
2022-11-03 16:26 ` [PATCH V6 1/8] block, bfq: split sync bfq_queues on a per-actuator basis Paolo Valente
2022-11-21 0:18 ` Damien Le Moal
2022-11-26 16:28 ` Paolo Valente
2022-11-28 14:32 ` Jens Axboe
2022-12-06 8:04 ` Paolo Valente
2022-11-03 16:26 ` [PATCH V6 2/8] block, bfq: forbid stable merging of queues associated with different actuators Paolo Valente
2022-11-21 0:20 ` Damien Le Moal
2022-11-03 16:26 ` [PATCH V6 3/8] block, bfq: move io_cq-persistent bfqq data into a dedicated struct Paolo Valente
2022-11-21 0:24 ` Damien Le Moal
2022-11-03 16:26 ` [PATCH V6 4/8] block, bfq: turn bfqq_data into an array in bfq_io_cq Paolo Valente
2022-11-21 0:39 ` Damien Le Moal
2022-12-06 8:00 ` Paolo Valente
2022-11-03 16:26 ` [PATCH V6 5/8] block, bfq: split also async bfq_queues on a per-actuator basis Paolo Valente
2022-11-21 0:52 ` Damien Le Moal
2022-11-03 16:26 ` [PATCH V6 6/8] block, bfq: retrieve independent access ranges from request queue Paolo Valente
2022-11-21 1:01 ` Damien Le Moal
2022-12-06 8:06 ` Paolo Valente
2022-12-06 8:29 ` Damien Le Moal
2022-12-06 8:41 ` Paolo Valente
2022-12-06 9:02 ` Damien Le Moal
2022-12-06 15:43 ` Paolo Valente
2022-12-06 23:34 ` Damien Le Moal
2022-12-08 10:43 ` Paolo Valente [this message]
2022-11-03 16:26 ` [PATCH V6 7/8] block, bfq: inject I/O to underutilized actuators Paolo Valente
2022-11-21 1:17 ` Damien Le Moal
2022-11-03 16:26 ` [PATCH V6 8/8] block, bfq: balance I/O injection among " Paolo Valente
2022-11-10 15:25 ` Arie van der Hoeven
2022-11-20 7:29 ` Paolo Valente
2022-11-20 22:06 ` Jens Axboe
2022-11-20 23:41 ` Damien Le Moal
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=41604669-2D56-4524-8FA1-527FEAD06B29@linaro.org \
--to=paolo.valente@linaro.org \
--cc=arie.vanderhoeven@seagate.com \
--cc=axboe@kernel.dk \
--cc=damien.lemoal@opensource.wdc.com \
--cc=f.gavioli97@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rory.c.chen@seagate.com \
/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).