All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Oleksandr Natalenko <oleksandr@natalenko.name>
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@redhat.com, ivan@ludios.org,
	169364@studenti.unimore.it,
	Serena Ziviani <ziviani.serena@gmail.com>
Subject: Re: [PATCH BUGFIX 1/1] block, bfq: add requeue-request hook
Date: Tue, 06 Feb 2018 14:46:08 +0100	[thread overview]
Message-ID: <1517924768.25841.32.camel@gmx.de> (raw)
In-Reply-To: <77124223e6116350a5184a5199850304@natalenko.name>

On Tue, 2018-02-06 at 13:16 +0100, Oleksandr Natalenko wrote:
> Hi.
>=20
> 06.02.2018 12:57, Mike Galbraith wrote:
> > Not me. =A0Box seems to be fairly sure that it is bfq.  Twice again box
> > went belly up on me in fairly short order with bfq, but seemed fine
> > with deadline.  I'm currently running deadline again, and box again
> > seems solid, thought I won't say _is_ solid until it's been happily
> > trundling along with deadline for a quite a bit longer.
>=20
> Sorry for the noise, but just to make it clear, are we talking about=20
> "deadline" or "mq-deadline" now?

mq-deadline.

WARNING: multiple messages have this Message-ID (diff)
From: Mike Galbraith <efault@gmx.de>
To: Oleksandr Natalenko <oleksandr@natalenko.name>
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@redhat.com, ivan@ludios.org, 169364@studenti.unimore.it,
	Serena Ziviani <ziviani.serena@gmail.com>
Subject: Re: [PATCH BUGFIX 1/1] block, bfq: add requeue-request hook
Date: Tue, 06 Feb 2018 14:46:08 +0100	[thread overview]
Message-ID: <1517924768.25841.32.camel@gmx.de> (raw)
In-Reply-To: <77124223e6116350a5184a5199850304@natalenko.name>

On Tue, 2018-02-06 at 13:16 +0100, Oleksandr Natalenko wrote:
> Hi.
> 
> 06.02.2018 12:57, Mike Galbraith wrote:
> > Not me.  Box seems to be fairly sure that it is bfq.  Twice again box
> > went belly up on me in fairly short order with bfq, but seemed fine
> > with deadline.  I'm currently running deadline again, and box again
> > seems solid, thought I won't say _is_ solid until it's been happily
> > trundling along with deadline for a quite a bit longer.
> 
> Sorry for the noise, but just to make it clear, are we talking about 
> "deadline" or "mq-deadline" now?

mq-deadline.

  reply	other threads:[~2018-02-06 13:46 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-05 19:05 [PATCH BUGFIX 0/1] block, bfq: handle requeues of I/O requests Paolo Valente
2018-02-05 19:05 ` [PATCH BUGFIX 1/1] block, bfq: add requeue-request hook Paolo Valente
2018-02-06  4:22   ` Mike Galbraith
2018-02-06  4:22     ` Mike Galbraith
2018-02-06  7:44   ` Oleksandr Natalenko
2018-02-06  7:56     ` Mike Galbraith
2018-02-06  7:56       ` Mike Galbraith
2018-02-06  8:37       ` Oleksandr Natalenko
2018-02-06  8:47         ` Mike Galbraith
2018-02-06  8:47           ` Mike Galbraith
2018-02-06  9:38       ` Paolo Valente
2018-02-06  9:38         ` Paolo Valente
2018-02-06 11:57         ` Mike Galbraith
2018-02-06 11:57           ` Mike Galbraith
2018-02-06 12:16           ` Oleksandr Natalenko
2018-02-06 13:46             ` Mike Galbraith [this message]
2018-02-06 13:46               ` Mike Galbraith
2018-02-06 14:07               ` Oleksandr Natalenko
2018-02-06 14:50                 ` Paolo Valente
2018-02-06 14:50                   ` Paolo Valente
2018-02-06 14:59                   ` Oleksandr Natalenko
2018-02-06 18:35                   ` Oleksandr Natalenko
2018-02-07  9:08                     ` Paolo Valente
2018-02-07  9:08                       ` Paolo Valente
2018-02-07  9:23                       ` Mike Galbraith
2018-02-07  9:23                         ` Mike Galbraith
2018-02-07  9:45                         ` Paolo Valente
2018-02-07 10:15                           ` Mike Galbraith
2018-02-07 10:27                             ` Paolo Valente
2018-02-07 10:27                               ` Paolo Valente
2018-02-07 10:31                               ` Mike Galbraith
2018-02-07 11:03                               ` Mike Galbraith
2018-02-07 11:12                                 ` Paolo Valente
2018-02-07 11:12                                   ` Paolo Valente
2018-02-07 11:22                                   ` Mike Galbraith
2018-02-07 11:27                               ` Paolo Valente
2018-02-07 15:50                                 ` Oleksandr Natalenko
2018-02-07 17:33                                   ` Paolo Valente
2018-02-07 17:33                                     ` Paolo Valente
2018-02-06 12:26           ` Paolo Valente
2018-02-06 12:26             ` Paolo Valente
2018-02-06 12:40             ` Paolo Valente
2018-02-06 12:40               ` Paolo Valente
2018-02-06 12:43             ` Holger Hoffstätte
2018-02-06 13:40               ` Holger Hoffstätte
2018-02-06 14:55                 ` Paolo Valente
2018-02-06 14:55                   ` Paolo Valente
2018-02-06 15:34                   ` Holger Hoffstätte
2018-02-06 14:07               ` Mike Galbraith
2018-02-06 14:07                 ` Mike Galbraith
2018-02-06 13:47             ` Mike Galbraith
2018-02-06 13:47               ` Mike Galbraith

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=1517924768.25841.32.camel@gmx.de \
    --to=efault@gmx.de \
    --cc=169364@studenti.unimore.it \
    --cc=alban.browaeys@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=bfq-iosched@googlegroups.com \
    --cc=broonie@kernel.org \
    --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=oleksandr@natalenko.name \
    --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.