From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
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,
glen.valante@linaro.org,
Gianmarco Lusvardi <glusvardi@posteo.net>,
Giulio Barabino <giuliobarabino99@gmail.com>,
Emiliano Maccaferri <inbox@emilianomaccaferri.com>
Subject: Re: [PATCH V8 3/8] block, bfq: move io_cq-persistent bfqq data into a dedicated struct
Date: Wed, 7 Dec 2022 08:22:50 +0900 [thread overview]
Message-ID: <52576133-b94e-e667-8410-33e44f3f37f1@opensource.wdc.com> (raw)
In-Reply-To: <20221206163203.30071-4-paolo.valente@linaro.org>
On 12/7/22 01:31, Paolo Valente wrote:
> With a multi-actuator drive, a process may get associated with multiple
> bfq_queues: one queue for each of the N actuators. So, the bfq_io_cq
> data structure must be able to accommodate its per-queue persistent
> information for N queues. Currently it stores this information for
> just one queue, in several scalar fields.
>
> This is a preparatory commit for moving to accommodating persistent
> information for N queues. In particular, this commit packs all the
> above scalar fields into a single data structure. Then there is now
> only one field, in bfq_io_cq, that stores all the above information. This
> scalar field will then be turned into an array by a following commit.
>
> Suggested-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
> Signed-off-by: Gianmarco Lusvardi <glusvardi@posteo.net>
> Signed-off-by: Giulio Barabino <giuliobarabino99@gmail.com>
> Signed-off-by: Emiliano Maccaferri <inbox@emilianomaccaferri.com>
> Signed-off-by: Paolo Valente <paolo.valente@linaro.org>
Reviewed-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2022-12-06 23:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 16:31 [PATCH V8 0/8] block, bfq: extend bfq to support multi-actuator drives Paolo Valente
2022-12-06 16:31 ` [PATCH V8 1/8] block, bfq: split sync bfq_queues on a per-actuator basis Paolo Valente
2022-12-06 16:31 ` [PATCH V8 2/8] block, bfq: forbid stable merging of queues associated with different actuators Paolo Valente
2022-12-06 16:31 ` [PATCH V8 3/8] block, bfq: move io_cq-persistent bfqq data into a dedicated struct Paolo Valente
2022-12-06 23:22 ` Damien Le Moal [this message]
2022-12-06 16:31 ` [PATCH V8 4/8] block, bfq: turn bfqq_data into an array in bfq_io_cq Paolo Valente
2022-12-06 16:32 ` [PATCH V8 5/8] block, bfq: split also async bfq_queues on a per-actuator basis Paolo Valente
2022-12-06 16:32 ` [PATCH V8 6/8] block, bfq: retrieve independent access ranges from request queue Paolo Valente
2022-12-06 16:32 ` [PATCH V8 7/8] block, bfq: inject I/O to underutilized actuators Paolo Valente
2022-12-06 16:32 ` [PATCH V8 8/8] block, bfq: balance I/O injection among " Paolo Valente
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=52576133-b94e-e667-8410-33e44f3f37f1@opensource.wdc.com \
--to=damien.lemoal@opensource.wdc.com \
--cc=arie.vanderhoeven@seagate.com \
--cc=axboe@kernel.dk \
--cc=giuliobarabino99@gmail.com \
--cc=glen.valante@linaro.org \
--cc=glusvardi@posteo.net \
--cc=inbox@emilianomaccaferri.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paolo.valente@linaro.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
all inboxes | Powered by JetHome®