From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Mike Galbraith <efault@gmx.de>,
Paolo Valente <paolo.valente@linaro.org>,
Jens Axboe <axboe@kernel.dk>, stable <stable@vger.kernel.org>
Subject: Re: [PATCH BUGFIX V3] block, bfq: add requeue-request hook
Date: Mon, 26 Feb 2018 21:10:40 +0100 [thread overview]
Message-ID: <1687637.lEvHKrKakh@natalenko.name> (raw)
In-Reply-To: <20180226194833.GG21453@kroah.com>
Hi.
On pondělí 26. února 2018 20:48:33 CET Greg KH wrote:
> Yes, that's fine with me.
>
> What ever happened to this? Do you have a list of patches I should
> apply? Or a patch series?
Here are BFQ commits that are already merged into Linus' tree:
a78773906147 block, bfq: add requeue-request hook
8a8747dc01ce block, bfq: limit sectors served with interactive weight raising
a52a69ea89dc block, bfq: limit tags for writes and async I/O
8993d445df38 block, bfq: fix occurrences of request finish method's old name
8abef10b3de1 bfq-iosched: don't call bfqg_and_blkg_put for !
CONFIG_BFQ_GROUP_IOSCHED
0d52af590552 block, bfq: release oom-queue ref to root group on exit
52257ffbfcaf block, bfq: put async queues for root bfq groups too
9b25bd0368d5 block, bfq: remove batches of confusing ifdefs
a34b024448eb block, bfq: consider also past I/O in soft real-time detection
4403e4e467c3 block, bfq: remove superfluous check in queue-merging setup
7b8fa3b900a0 block, bfq: let a queue be merged only shortly after starting I/O
1be6e8a964ee block, bfq: check low_latency flag in bfq_bfqq_save_state()
05e902835616 block, bfq: add missing rq_pos_tree update on rq removal
f0ba5ea2fe45 block, bfq: increase threshold to deem I/O as random
Paolo, could you please confirm we are not missing anything here?
Oleksandr
next prev parent reply other threads:[~2018-02-26 20:10 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 21:19 [PATCH BUGFIX V3] block, bfq: add requeue-request hook Paolo Valente
2018-02-07 22:18 ` Jens Axboe
2018-02-08 7:16 ` Paolo Valente
2018-02-08 7:16 ` Paolo Valente
2018-02-09 13:21 ` Oleksandr Natalenko
2018-02-09 17:17 ` Jens Axboe
2018-02-09 17:29 ` Mike Galbraith
2018-02-10 8:29 ` Oleksandr Natalenko
2018-02-10 8:29 ` Oleksandr Natalenko
2018-02-12 7:24 ` Paolo Valente
2018-02-12 7:24 ` Paolo Valente
2018-02-12 11:22 ` Mike Galbraith
2018-02-12 12:48 ` Oleksandr Natalenko
2018-02-13 5:02 ` Mike Galbraith
2018-02-13 5:46 ` Paolo Valente
2018-02-13 6:42 ` Mike Galbraith
2018-02-13 6:50 ` Mike Galbraith
2018-02-13 8:15 ` Paolo Valente
2018-02-13 14:30 ` Mike Galbraith
2018-02-14 5:58 ` Mike Galbraith
2018-02-14 7:04 ` Mike Galbraith
2018-02-14 7:15 ` Mike Galbraith
2018-02-14 8:56 ` Paolo Valente
2018-02-14 9:55 ` Oleksandr Natalenko
2018-02-14 13:25 ` Mike Galbraith
2018-02-14 15:19 ` Jens Axboe
2018-02-14 15:39 ` Paolo Valente
2018-02-14 15:44 ` Jens Axboe
2018-02-15 18:13 ` Paolo Valente
2018-02-16 5:39 ` Mike Galbraith
2018-02-16 7:16 ` Paolo Valente
2018-02-16 7:20 ` Paolo Valente
2018-02-17 5:30 ` Mike Galbraith
2018-02-17 5:33 ` Mike Galbraith
2018-02-19 5:34 ` Mike Galbraith
2018-02-19 6:05 ` Oleksandr Natalenko
2018-02-19 7:09 ` Mike Galbraith
2018-02-19 7:58 ` Mike Galbraith
2018-02-19 9:37 ` Paolo Valente
2018-02-19 13:18 ` Mike Galbraith
2018-02-17 5:39 ` Mike Galbraith
2018-02-26 19:48 ` Greg KH
2018-02-26 20:10 ` Oleksandr Natalenko [this message]
2018-02-26 20:18 ` Jens Axboe
2018-02-23 15:07 ` Ming Lei
2018-02-23 15:41 ` Paolo Valente
2018-02-23 15:41 ` Paolo Valente
2018-02-23 16:17 ` Ming Lei
2018-02-24 7:54 ` Paolo Valente
2018-02-24 7:54 ` Paolo Valente
2018-02-24 12:05 ` Ming Lei
2018-02-24 16:15 ` Paolo Valente
2018-02-24 16:15 ` 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=1687637.lEvHKrKakh@natalenko.name \
--to=oleksandr@natalenko.name \
--cc=axboe@kernel.dk \
--cc=efault@gmx.de \
--cc=gregkh@linuxfoundation.org \
--cc=paolo.valente@linaro.org \
--cc=stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.