All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Jens Axboe <axboe@fb.com>, linux-block@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>,
	Omar Sandoval <osandov@fb.com>,
	Jozef Mikovic <jmikovic@redhat.com>
Subject: Re: [PATCH 0/4] blk-mq-sched: allow to use hw tag for sched
Date: Mon, 17 Apr 2017 00:03:53 +0800	[thread overview]
Message-ID: <20170416160352.GA6349@ming.t460p> (raw)
In-Reply-To: <20170415123825.32716-1-ming.lei@redhat.com>

On Sat, Apr 15, 2017 at 08:38:21PM +0800, Ming Lei wrote:
> The 1st patch enhances BLK_MQ_F_NO_SCHED so that we can't change/
> show available io schedulers on devices which don't support io
> scheduler.
> 
> The 2nd patch passes BLK_MQ_F_NO_SCHED for avoiding one regression
> on mtip32xx, which is introduced by blk-mq io scheduler.
> 
> The last two patches introduce BLK_MQ_F_SCHED_USE_HW_TAG so that
> we can allow to use hardware tag for scheduler, then mq-deadline
> can work well on mtip32xx. Even though other devices with enough
> hardware tag space can benefit from this feature too.
> 
> The 1st two patches aims on v4.11, and the last two are for
> v4.12.

Please ignore this patchset, and I will post another serial for
mtip32xx fix.

thanks,
Ming

  parent reply	other threads:[~2017-04-16 16:04 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-15 12:38 [PATCH 0/4] blk-mq-sched: allow to use hw tag for sched Ming Lei
2017-04-15 12:38 ` [PATCH 1/4] block: respect BLK_MQ_F_NO_SCHED Ming Lei
2017-04-15 12:38 ` [PATCH 2/4] mtip32xx: pass BLK_MQ_F_NO_SCHED Ming Lei
2017-04-15 12:38 ` [PATCH 3/4] blk-mq: introduce BLK_MQ_F_SCHED_USE_HW_TAG Ming Lei
2017-04-15 12:38 ` [PATCH 4/4] mtip32xx: use BLK_MQ_F_USE_SCHED_TAG Ming Lei
2017-04-16 16:03 ` Ming Lei [this message]
2017-04-17 17:30   ` [PATCH 0/4] blk-mq-sched: allow to use hw tag for sched Omar Sandoval
2017-04-19  1:10     ` Ming Lei
2017-04-19 20:17 ` Jens Axboe
2017-04-20  0:44   ` Ming Lei
2017-04-20  0:55     ` Jens Axboe
2017-04-20  1:03       ` Ming Lei
2017-04-20  4:54         ` Christoph Hellwig
2017-04-20  8:30           ` Ming Lei
2017-04-26 10:48             ` Ming Lei
2017-04-26 18:15               ` Jens Axboe
2017-04-26 18:22                 ` Jens Axboe
2017-04-27  3:14                   ` Ming Lei
2017-04-27 13:49                     ` Jens Axboe
2017-04-27 15:20                       ` Christoph Hellwig
2017-04-27 15:46                         ` Jens Axboe
2017-04-27 21:40                           ` Jens Axboe
2017-04-27  6:32               ` Christoph Hellwig
2017-04-20 16:10           ` Jens Axboe
2017-04-21 10:54             ` Christoph Hellwig

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=20170416160352.GA6349@ming.t460p \
    --to=ming.lei@redhat.com \
    --cc=axboe@fb.com \
    --cc=hch@infradead.org \
    --cc=jmikovic@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=osandov@fb.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.