From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Ming Lei <ming.lei@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
linux-block@vger.kernel.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: Thu, 27 Apr 2017 08:20:50 -0700 [thread overview]
Message-ID: <20170427152050.GA733@infradead.org> (raw)
In-Reply-To: <9990a1b5-6c4c-7308-8f38-22bb67c08ff1@kernel.dk>
On Thu, Apr 27, 2017 at 06:49:43AM -0700, Jens Axboe wrote:
> Thanks Ming, I've added that patch and your patch to initialize the cmd
> at runtime.
I really think this is the wrong fix, and doing these sort of band-aids
just will lead to further problems done the road.
next prev parent reply other threads:[~2017-04-27 15:20 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 ` [PATCH 0/4] blk-mq-sched: allow to use hw tag for sched Ming Lei
2017-04-17 17:30 ` 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 [this message]
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=20170427152050.GA733@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=jmikovic@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--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.