From: Christoph Hellwig <hch@lst.de>
To: Matias Bjorling <m@bjorling.me>
Cc: Jens Axboe <axboe@fb.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [RFC] blk-mq: support for shared tags
Date: Thu, 3 Apr 2014 09:36:31 +0200 [thread overview]
Message-ID: <20140403073631.GA26921@lst.de> (raw)
In-Reply-To: <533CDF24.9030902@bjorling.me>
On Wed, Apr 02, 2014 at 09:10:12PM -0700, Matias Bjorling wrote:
> For the nvme driver, there's a single admin queue, which is outside
> blk-mq's control, and the X normal queues. Should we allow the shared
> tags structure to be used (get/put) for the admin queue, without
> initializing blk-mq? or should the drivers simply implement their own
> tags for their admin queue?
I'd still create a request_queue for the internal queue, just not register
a block device for it. For example SCSI sets up queues for each LUN
found, but only a subset actually is exposed as a block device.
next prev parent reply other threads:[~2014-04-03 7:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 14:46 [RFC] blk-mq: support for shared tags Christoph Hellwig
2014-03-31 14:46 ` [PATCH 1/4] blk->mq: stop pre-initializing req->special Christoph Hellwig
2014-03-31 14:46 ` [PATCH 2/4] blk-mq: initialize request on allocation Christoph Hellwig
2014-03-31 14:46 ` [PATCH 3/4] blk-mq: move request structures into struct blk_mq_tags Christoph Hellwig
2014-04-09 16:23 ` Jens Axboe
2014-04-10 10:01 ` Christoph Hellwig
2014-04-11 2:42 ` Jens Axboe
2014-04-11 7:33 ` Christoph Hellwig
2014-04-11 13:56 ` Jens Axboe
2014-03-31 14:46 ` [PATCH 4/4] blk-mq: support shared tag maps Christoph Hellwig
2014-04-02 0:16 ` [RFC] blk-mq: support for shared tags Matias Bjorling
2014-04-02 7:46 ` Christoph Hellwig
2014-04-03 4:10 ` Matias Bjorling
2014-04-03 7:36 ` Christoph Hellwig [this message]
2014-04-03 16:45 ` Matias Bjorling
2014-04-03 18:01 ` Christoph Hellwig
2014-04-03 21:47 ` Matias Bjorling
2014-04-04 15:19 ` 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=20140403073631.GA26921@lst.de \
--to=hch@lst.de \
--cc=axboe@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=m@bjorling.me \
/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).