From: Jens Axboe <axboe@kernel.dk>
To: Paolo Valente <paolo.valente@linaro.org>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
arie.vanderhoeven@seagate.com, rory.c.chen@seagate.com,
glen.valante@linaro.org, damien.lemoal@opensource.wdc.com
Subject: Re: [PATCH V13 0/8] block, bfq: extend bfq to support multi-actuator drives
Date: Mon, 2 Jan 2023 09:53:34 -0700 [thread overview]
Message-ID: <9a01e386-0fb5-b074-a7b1-7e4bcf1ca204@kernel.dk> (raw)
In-Reply-To: <20221229203707.68458-1-paolo.valente@linaro.org>
On 12/29/22 1:36 PM, Paolo Valente wrote:
> Hi,
> here is the V13, it differs from V12 in that it applies the
> recommendation by Damien in [2].
This doesn't apply to current master. Can you send one that
does?
--
Jens Axboe
next prev parent reply other threads:[~2023-01-02 16:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-29 20:36 Paolo Valente
2022-12-29 20:37 ` [PATCH V13 1/8] block, bfq: split sync bfq_queues on a per-actuator basis Paolo Valente
2022-12-29 20:37 ` [PATCH V13 2/8] block, bfq: forbid stable merging of queues associated with different actuators Paolo Valente
2022-12-29 20:37 ` [PATCH V13 3/8] block, bfq: move io_cq-persistent bfqq data into a dedicated struct Paolo Valente
2022-12-29 20:37 ` [PATCH V13 4/8] block, bfq: turn bfqq_data into an array in bfq_io_cq Paolo Valente
2022-12-29 20:37 ` [PATCH V13 5/8] block, bfq: split also async bfq_queues on a per-actuator basis Paolo Valente
2022-12-29 20:37 ` [PATCH V13 6/8] block, bfq: retrieve independent access ranges from request queue Paolo Valente
2022-12-29 20:37 ` [PATCH V13 7/8] block, bfq: inject I/O to underutilized actuators Paolo Valente
2022-12-29 20:37 ` [PATCH V13 8/8] block, bfq: balance I/O injection among " Paolo Valente
2023-01-02 16:53 ` Jens Axboe [this message]
2023-01-03 14:54 ` [PATCH V13 0/8] block, bfq: extend bfq to support multi-actuator drives 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=9a01e386-0fb5-b074-a7b1-7e4bcf1ca204@kernel.dk \
--to=axboe@kernel.dk \
--cc=arie.vanderhoeven@seagate.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=glen.valante@linaro.org \
--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®