From: Christoph Hellwig <hch@infradead.org>
To: Hannes Reinecke <hare@suse.de>
Cc: Christoph Hellwig <hch@infradead.org>,
Mike Snitzer <snitzer@redhat.com>,
dm-devel-redhat.com@suse.de,
Damien Le Moal <damien.lemoal@hgst.com>,
linux-scsi@vger.kernel.org, linux-block@vger.kernel.org,
Jens Axboe <axboe@fb.com>
Subject: Re: [PATCH 1/3] block: add flag for single-threaded submission
Date: Thu, 21 Jul 2016 07:38:08 -0700 [thread overview]
Message-ID: <20160721143808.GA29902@infradead.org> (raw)
In-Reply-To: <0030fdc3-bd7d-2e91-56ae-c20086a55d22@suse.de>
On Thu, Jul 21, 2016 at 08:37:10AM +0200, Hannes Reinecke wrote:
> Looking closer do I _really_ need that for blk-mq?
> >From my understanding any hctx can only run on one dedicated cpu, to
> which the hctx is bound.
That's not the case. A hctx exists for each hardware queue, and a CPU
must be mapped to a hctx. So if you have less hctx than CPUs (e.g. just
one) you have multiple CPUs that could submit on a hctx.
next prev parent reply other threads:[~2016-07-21 14:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 14:02 [PATCH 0/3] dm-zoned target for ZBC devices Hannes Reinecke
2016-07-19 14:02 ` [PATCH 1/3] block: add flag for single-threaded submission Hannes Reinecke
2016-07-20 1:13 ` Damien Le Moal
2016-07-21 5:54 ` Christoph Hellwig
2016-07-21 6:01 ` Hannes Reinecke
2016-07-21 6:37 ` Hannes Reinecke
2016-07-21 7:10 ` Damien Le Moal
2016-07-21 14:38 ` Christoph Hellwig [this message]
2016-07-19 14:02 ` [PATCH 2/3] sd: enable single-threaded I/O submission for zoned devices Hannes Reinecke
2016-07-20 1:15 ` Damien Le Moal
2016-07-19 14:02 ` [PATCH 3/3] dm-zoned: New device mapper target for zoned block devices Hannes Reinecke
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=20160721143808.GA29902@infradead.org \
--to=hch@infradead.org \
--cc=axboe@fb.com \
--cc=damien.lemoal@hgst.com \
--cc=dm-devel-redhat.com@suse.de \
--cc=hare@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=snitzer@redhat.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).