From: Jens Axboe <axboe@kernel.dk>
To: Paolo Valente <paolo.valente@linaro.org>
Cc: 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>,
Glen Valante <glen.valante@linaro.org>,
Damien Le Moal <damien.lemoal@opensource.wdc.com>
Subject: Re: [PATCH V10 0/8] block, bfq: extend bfq to support multi-actuator drives
Date: Tue, 13 Dec 2022 08:43:09 -0700 [thread overview]
Message-ID: <0bcf7776-59d7-53ef-bfd0-449940a05161@kernel.dk> (raw)
In-Reply-To: <A0328388-7C6B-46A4-A05E-DCD6D91334AE@linaro.org>
On 12/13/22 8:40?AM, Paolo Valente wrote:
> Hi Jens, Damien,
> can we consider this for 6.2?
No, it's too late to queue up for 6.2, even when it was posted on
Friday. Bigger changes like that should be in my tree at least a week
before the merge window opens, preferably two (or somewhere in between).
I already tagged the main 6.2 block changes on Friday, and the pull
request has been sent out.
--
Jens Axboe
next prev parent reply other threads:[~2022-12-13 15:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 9:44 [PATCH V10 0/8] block, bfq: extend bfq to support multi-actuator drives Paolo Valente
2022-12-09 9:44 ` [PATCH V10 1/8] block, bfq: split sync bfq_queues on a per-actuator basis Paolo Valente
2022-12-16 0:00 ` Damien Le Moal
2022-12-20 13:10 ` Paolo Valente
2022-12-21 0:50 ` Damien Le Moal
2022-12-21 10:13 ` Paolo Valente
2022-12-21 10:30 ` Paolo Valente
2022-12-09 9:44 ` [PATCH V10 2/8] block, bfq: forbid stable merging of queues associated with different actuators Paolo Valente
2022-12-09 9:44 ` [PATCH V10 3/8] block, bfq: move io_cq-persistent bfqq data into a dedicated struct Paolo Valente
2022-12-09 9:44 ` [PATCH V10 4/8] block, bfq: turn bfqq_data into an array in bfq_io_cq Paolo Valente
2022-12-09 9:44 ` [PATCH V10 5/8] block, bfq: split also async bfq_queues on a per-actuator basis Paolo Valente
2022-12-09 9:44 ` [PATCH V10 6/8] block, bfq: retrieve independent access ranges from request queue Paolo Valente
2022-12-09 9:44 ` [PATCH V10 7/8] block, bfq: inject I/O to underutilized actuators Paolo Valente
2022-12-09 9:44 ` [PATCH V10 8/8] block, bfq: balance I/O injection among " Paolo Valente
2022-12-16 1:36 ` Damien Le Moal
2022-12-13 15:40 ` [PATCH V10 0/8] block, bfq: extend bfq to support multi-actuator drives Paolo Valente
2022-12-13 15:43 ` Jens Axboe [this message]
2022-12-13 17:10 ` Arie van der Hoeven
2022-12-13 17:17 ` Jens Axboe
2022-12-15 15:04 ` Paolo Valente
2022-12-15 15:12 ` Jens Axboe
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=0bcf7776-59d7-53ef-bfd0-449940a05161@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