All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: Mike Galbraith <efault@gmx.de>
Cc: Paolo Valente <paolo.valente@linaro.org>,
	Jens Axboe <axboe@kernel.dk>,
	linux-block <linux-block@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Mark Brown <broonie@kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	'Paolo Valente' via bfq-iosched <bfq-iosched@googlegroups.com>,
	Alban Browaeys <alban.browaeys@gmail.com>,
	Ming Lei <ming.lei@redhat.com>, Ivan Kozik <ivan@ludios.org>,
	169364@studenti.unimore.it, holger@applied-asynchrony.com,
	Serena Ziviani <ziviani.serena@gmail.com>
Subject: Re: [PATCH BUGFIX V3] block, bfq: add requeue-request hook
Date: Sat, 10 Feb 2018 09:29:29 +0100	[thread overview]
Message-ID: <6394471.U0O273vb9H@natalenko.name> (raw)
In-Reply-To: <1518197379.26824.31.camel@gmx.de>

Hi.

On p=E1tek 9. =FAnora 2018 18:29:39 CET Mike Galbraith wrote:
> On Fri, 2018-02-09 at 14:21 +0100, Oleksandr Natalenko wrote:
> > In addition to this I think it should be worth considering CC'ing Greg
> > to pull this fix into 4.15 stable tree.
>=20
> This isn't one he can cherry-pick, some munging required, in which case
> he usually wants a properly tested backport.
>=20
> 	-Mike

Maybe, this could be a good opportunity to push all the pending BFQ patches=
=20
into the stable 4.15 branch? Because IIUC currently BFQ in 4.15 is just=20
unusable.

Paolo?

=2D--

block, bfq: add requeue-request hook
bfq-iosched: don't call bfqg_and_blkg_put for !CONFIG_BFQ_GROUP_IOSCHED
block, bfq: release oom-queue ref to root group on exit
block, bfq: put async queues for root bfq groups too
block, bfq: limit sectors served with interactive weight raising
block, bfq: limit tags for writes and async I/O
block, bfq: increase threshold to deem I/O as random
block, bfq: remove superfluous check in queue-merging setup
block, bfq: let a queue be merged only shortly after starting I/O
block, bfq: check low_latency flag in bfq_bfqq_save_state()
block, bfq: add missing rq_pos_tree update on rq removal
block, bfq: fix occurrences of request finish method's old name
block, bfq: consider also past I/O in soft real-time detection
block, bfq: remove batches of confusing ifdefs

WARNING: multiple messages have this Message-ID (diff)
From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: Mike Galbraith <efault@gmx.de>
Cc: Paolo Valente <paolo.valente@linaro.org>,
	Jens Axboe <axboe@kernel.dk>,
	linux-block <linux-block@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Mark Brown <broonie@kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	"'Paolo Valente' via bfq-iosched" <bfq-iosched@googlegroups.com>,
	Alban Browaeys <alban.browaeys@gmail.com>,
	Ming Lei <ming.lei@redhat.com>, Ivan Kozik <ivan@ludios.org>,
	169364@studenti.unimore.it, holger@applied-asynchrony.com,
	Serena Ziviani <ziviani.serena@gmail.com>
Subject: Re: [PATCH BUGFIX V3] block, bfq: add requeue-request hook
Date: Sat, 10 Feb 2018 09:29:29 +0100	[thread overview]
Message-ID: <6394471.U0O273vb9H@natalenko.name> (raw)
In-Reply-To: <1518197379.26824.31.camel@gmx.de>

Hi.

On pátek 9. února 2018 18:29:39 CET Mike Galbraith wrote:
> On Fri, 2018-02-09 at 14:21 +0100, Oleksandr Natalenko wrote:
> > In addition to this I think it should be worth considering CC'ing Greg
> > to pull this fix into 4.15 stable tree.
> 
> This isn't one he can cherry-pick, some munging required, in which case
> he usually wants a properly tested backport.
> 
> 	-Mike

Maybe, this could be a good opportunity to push all the pending BFQ patches 
into the stable 4.15 branch? Because IIUC currently BFQ in 4.15 is just 
unusable.

Paolo?

---

block, bfq: add requeue-request hook
bfq-iosched: don't call bfqg_and_blkg_put for !CONFIG_BFQ_GROUP_IOSCHED
block, bfq: release oom-queue ref to root group on exit
block, bfq: put async queues for root bfq groups too
block, bfq: limit sectors served with interactive weight raising
block, bfq: limit tags for writes and async I/O
block, bfq: increase threshold to deem I/O as random
block, bfq: remove superfluous check in queue-merging setup
block, bfq: let a queue be merged only shortly after starting I/O
block, bfq: check low_latency flag in bfq_bfqq_save_state()
block, bfq: add missing rq_pos_tree update on rq removal
block, bfq: fix occurrences of request finish method's old name
block, bfq: consider also past I/O in soft real-time detection
block, bfq: remove batches of confusing ifdefs

  reply	other threads:[~2018-02-10  8:29 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 [this message]
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
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=6394471.U0O273vb9H@natalenko.name \
    --to=oleksandr@natalenko.name \
    --cc=169364@studenti.unimore.it \
    --cc=alban.browaeys@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=bfq-iosched@googlegroups.com \
    --cc=broonie@kernel.org \
    --cc=efault@gmx.de \
    --cc=holger@applied-asynchrony.com \
    --cc=ivan@ludios.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=paolo.valente@linaro.org \
    --cc=ulf.hansson@linaro.org \
    --cc=ziviani.serena@gmail.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 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.