From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@fb.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Ming Lei <ming.lei@redhat.com>,
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: Fri, 21 Apr 2017 03:54:46 -0700 [thread overview]
Message-ID: <20170421105446.GA31499@infradead.org> (raw)
In-Reply-To: <68f95811-380e-21f8-cdcb-2e47c6af4d56@fb.com>
On Thu, Apr 20, 2017 at 10:10:59AM -0600, Jens Axboe wrote:
> Right, the hardware doesn't require it at all, it's just an oddity
> of the driver that it hardwares tag 0 as an internal tag. That could
> definitely get cleaned up.
That's exactly what I suspect, especially as the hardware is AHCI
on stereoids. But I'd need a data sheet to confirm my suspicion.
prev parent reply other threads:[~2017-04-21 10:54 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
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 [this message]
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=20170421105446.GA31499@infradead.org \
--to=hch@infradead.org \
--cc=axboe@fb.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).