From: Jens Axboe <axboe@kernel.dk>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Christoph Hellwig <hch@lst.de>,
don.brace@microsemi.com, linux-scsi@vger.kernel.org,
linux-block@vger.kernel.org
Subject: Re: [PATCH 1/3] blk-mq: export blk_mq_map_queues
Date: Tue, 1 Nov 2016 10:02:51 -0600 [thread overview]
Message-ID: <20161101160251.GA9797@kernel.dk> (raw)
In-Reply-To: <yq1lgx319jl.fsf@sermon.lab.mkp.net>
On Tue, Nov 01 2016, Martin K. Petersen wrote:
> >>>>> "Christoph" == Christoph Hellwig <hch@lst.de> writes:
>
> Christoph> This will allow SCSI to have a single blk_mq_ops structure
> Christoph> that either lets the LLDD map the queues to PCIe MSIx vectors
> Christoph> or use the default.
>
> Jens, any objection to me funneling this change through the SCSI tree?
No, that's fine, you can add my reviewed-by.
--
Jens Axboe
next prev parent reply other threads:[~2016-11-01 16:02 UTC|newest]
Thread overview: 14+ 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 [this message]
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 ` expose queue the queue mapping for SCSI drivers V2 Martin K. Petersen
-- strict thread matches above, loose matches on Subject: below --
2016-10-15 8:47 expose queue the queue mapping for SCSI drivers Christoph Hellwig
2016-10-15 8:47 ` [PATCH 1/3] blk-mq: export blk_mq_map_queues Christoph Hellwig
2016-10-15 11:45 ` Hannes Reinecke
2016-10-15 11:45 ` Hannes Reinecke
2016-10-17 7:29 ` Johannes Thumshirn
2016-10-17 7:29 ` Johannes Thumshirn
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=20161101160251.GA9797@kernel.dk \
--to=axboe@kernel.dk \
--cc=don.brace@microsemi.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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 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.