From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Christoph Hellwig <hch@lst.de>
Cc: martin.petersen@oracle.com, don.brace@microsemi.com,
axboe@kernel.dk, linux-scsi@vger.kernel.org,
linux-block@vger.kernel.org
Subject: Re: expose queue the queue mapping for SCSI drivers V2
Date: Tue, 01 Nov 2016 13:37:46 -0400 [thread overview]
Message-ID: <yq1vaw7yuc5.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <1478009569-19026-1-git-send-email-hch@lst.de> (Christoph Hellwig's message of "Tue, 1 Nov 2016 08:12:46 -0600")
>>>>> "Christoph" == Christoph Hellwig <hch@lst.de> writes:
Christoph> In 4.9 I've added support in the interrupt layer to
Christoph> automatically assign the interrupt affinity at interrupt
Christoph> allocation time, and expose that information to blk-mq.
Christoph> This series extents that so that SCSI driver can pass on the
Christoph> information as well. The SCSI part is fairly trivial,
Christoph> although we need to also export the default queue mapping
Christoph> function in blk-mq to keep things simple.
Christoph> I've also converted over the smartpqi driver as an example as
Christoph> it's the easiest of the multiqueue SCSI drivers to convert.
Applied to 4.10/scsi-queue.
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2016-11-01 17:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 14:12 expose queue the queue mapping for SCSI drivers V2 Christoph Hellwig
2016-11-01 14:12 ` [PATCH 1/3] blk-mq: export blk_mq_map_queues Christoph Hellwig
2016-11-01 15:53 ` Martin K. Petersen
2016-11-01 16:02 ` Jens Axboe
2016-11-01 16:00 ` Sagi Grimberg
2016-11-01 14:12 ` [PATCH 2/3] scsi: allow LLDDs to expose the queue mapping to blk-mq Christoph Hellwig
2016-11-01 16:01 ` Sagi Grimberg
2016-11-01 14:12 ` [PATCH 3/3] smartpqi: switch to pci_alloc_irq_vectors Christoph Hellwig
2016-11-01 17:37 ` Martin K. Petersen [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=yq1vaw7yuc5.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=axboe@kernel.dk \
--cc=don.brace@microsemi.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/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