From: Hannes Reinecke <hare@suse.de>
To: Sagi Grimberg <sagig@dev.mellanox.co.il>,
Bart Van Assche <bart.vanassche@sandisk.com>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>,
"linux-scsi@vger.kernel.org" <Linux-scsi@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [LSF/MM TOPIC] multiqueue and interrupt assignment
Date: Wed, 3 Feb 2016 16:03:19 +0100 [thread overview]
Message-ID: <56B216B7.309@suse.de> (raw)
In-Reply-To: <56B20173.10006@dev.mellanox.co.il>
On 02/03/2016 02:32 PM, Sagi Grimberg wrote:
>
>> Indeed, something like this.
>> Quite some issues would be solved if we could push a hctx mapping
>> into blk-mq, instead of having it assign its own made-up one.
>
> For that you can provide your own .map_queue in blk_mq_ops I think
> (no one does that at the moment). This requires every driver to
> implement it's own routine (probably with a similar logic) though...
And at the same time direct interrupt assigment from the driver is
frowned upon ... feels a bit stupid, having to setup a cpu-to-queue
assigment (which typically is identical to the cpu-to-msix
assignment), then pass this information to blk-mq, which then passed
it to user-space, which then uses the information to setup a
cpu-to-msix assignment.
There is room for improvement there ...
Are there any plans addressing this in blk-mq?
What does NVMe and virtio do?
Cheers,
Hannes
--
Dr. Hannes Reinecke Teamlead Storage & Networking
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-02-03 15:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 16:31 [LSF/MM TOPIC] multiqueue and interrupt assignment Hannes Reinecke
2016-02-02 18:23 ` Bart Van Assche
2016-02-03 12:57 ` Sagi Grimberg
2016-02-03 13:13 ` Hannes Reinecke
2016-02-03 13:32 ` Sagi Grimberg
2016-02-03 15:03 ` Hannes Reinecke [this message]
2016-03-03 7:59 ` Ming Lei
2016-02-02 18:45 ` Elliott, Robert (Persistent Memory)
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=56B216B7.309@suse.de \
--to=hare@suse.de \
--cc=Linux-scsi@vger.kernel.org \
--cc=bart.vanassche@sandisk.com \
--cc=linux-block@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=sagig@dev.mellanox.co.il \
/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.