linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Valente <paolo.valente@linaro.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	Paolo Valente <paolo.valente@linaro.org>
Subject: [PATCH V5 0/8] block, bfq: extend bfq to support multi-actuator drives
Date: Sun, 30 Oct 2022 11:02:52 +0100	[thread overview]
Message-ID: <20221030100300.3085-1-paolo.valente@linaro.org> (raw)

Hi,
this V5 differs from V4 in that it addresses the issues reported in
[2] and [3].

Here is the whole description of this patch series again.  This
extension addresses the following issue. Single-LUN multi-actuator
SCSI drives, as well as all multi-actuator SATA drives appear as a
single device to the I/O subsystem [1].  Yet they address commands to
different actuators internally, as a function of Logical Block
Addressing (LBAs). A given sector is reachable by only one of the
actuators. For example, Seagate’s Serial Advanced Technology
Attachment (SATA) version contains two actuators and maps the lower
half of the SATA LBA space to the lower actuator and the upper half to
the upper actuator.

Evidently, to fully utilize actuators, no actuator must be left idle
or underutilized while there is pending I/O for it. To reach this
goal, the block layer must somehow control the load of each actuator
individually. This series enriches BFQ with such a per-actuator
control, as a first step. Then it also adds a simple mechanism for
guaranteeing that actuators with pending I/O are never left idle.

See [1] for a more detailed overview of the problem and of the
solutions implemented in this patch series. There you will also find
some preliminary performance results.

Thanks,
Paolo

[1] https://www.linaro.org/blog/budget-fair-queueing-bfq-linux-io-scheduler-optimizations-for-multi-actuator-sata-hard-drives/
[2] https://lore.kernel.org/lkml/202210212014.ynAHDVJU-lkp@intel.com/t/#mda5d00db9eb78ea698e7d0269b78ac57d134181e
[3] https://lore.kernel.org/lkml/202210212014.ynAHDVJU-lkp@intel.com/t/#m31c1d2403d0ae584b8a99733b29233d350cd9628

Davide Zini (3):
  block, bfq: split also async bfq_queues on a per-actuator basis
  block, bfq: inject I/O to underutilized actuators
  block, bfq: balance I/O injection among underutilized actuators

Federico Gavioli (1):
  block, bfq: retrieve independent access ranges from request queue

Paolo Valente (4):
  block, bfq: split sync bfq_queues on a per-actuator basis
  block, bfq: forbid stable merging of queues associated with different
    actuators
  block, bfq: move io_cq-persistent bfqq data into a dedicated struct
  block, bfq: turn bfqq_data into an array in bfq_io_cq

 block/bfq-cgroup.c  |  97 ++++----
 block/bfq-iosched.c | 533 ++++++++++++++++++++++++++++++--------------
 block/bfq-iosched.h | 141 +++++++++---
 block/bfq-wf2q.c    |   2 +-
 4 files changed, 539 insertions(+), 234 deletions(-)

--
2.20.1

             reply	other threads:[~2022-10-30 10:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-30 10:02 Paolo Valente [this message]
2022-10-30 10:02 ` [PATCH V5 1/8] block, bfq: split sync bfq_queues on a per-actuator basis Paolo Valente
2022-10-30 10:02 ` [PATCH V5 2/8] block, bfq: forbid stable merging of queues associated with different actuators Paolo Valente
2022-10-30 10:02 ` [PATCH V5 3/8] block, bfq: move io_cq-persistent bfqq data into a dedicated struct Paolo Valente
2022-10-30 11:08   ` kernel test robot
2022-10-30 23:43   ` Damien Le Moal
2022-10-30 10:02 ` [PATCH V5 4/8] block, bfq: turn bfqq_data into an array in bfq_io_cq Paolo Valente
2022-10-30 10:02 ` [PATCH V5 5/8] block, bfq: split also async bfq_queues on a per-actuator basis Paolo Valente
2022-10-30 10:02 ` [PATCH V5 6/8] block, bfq: retrieve independent access ranges from request queue Paolo Valente
2022-10-30 10:02 ` [PATCH V5 7/8] block, bfq: inject I/O to underutilized actuators Paolo Valente
2022-10-30 10:03 ` [PATCH V5 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=20221030100300.3085-1-paolo.valente@linaro.org \
    --to=paolo.valente@linaro.org \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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).