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 [email protected] +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 [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
