From: Mauricio Faria de Oliveira <mauricfo@linux.vnet.ibm.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-scsi@vger.kernel.org, dick.kennedy@broadcom.com,
james.smart@broadcom.com
Subject: Re: [PATCH 1/2] lpfc: support for CPU phys_id and core_id on PowerPC64
Date: Tue, 21 Jun 2016 14:42:09 -0300 [thread overview]
Message-ID: <57697C71.3060109@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160621142902.GA10597@infradead.org>
On 06/21/2016 11:29 AM, Christoph Hellwig wrote:
> I really don't think this sort of low level information has business
> in a low level driver. I've been trying to put some infrastructure
> together to move this to the core kernel [1], and it would be good to
> help use this in more drivers. Especially given that lpfc may use
> blk-mq which will not respect this current assignment for the queue
> mapping.
Agree.
However, this patchset targets the non blk-mq/scsi-mq usage of the
lpfc driver, which falls back to CPU-number/queue-number mapping.
This turns out to still be the case w/ some distros where ppc64/le
usually runs, on which it would be easier to adapt this relatively
small change than moving forward w/ blk-mq/scsi-mq, for example --
even if the latter is clearly a superior approach.
> [1] http://lists.infradead.org/pipermail/linux-nvme/2016-June/005012.html
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
next prev parent reply other threads:[~2016-06-21 17:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1464813809-22066-1-git-send-email-mauricfo@linux.vnet.ibm.com>
2016-06-01 20:43 ` [PATCH 1/2] lpfc: support for CPU phys_id and core_id on PowerPC64 Mauricio Faria de Oliveira
2016-06-21 14:29 ` Christoph Hellwig
2016-06-21 17:42 ` Mauricio Faria de Oliveira [this message]
2016-06-22 2:16 ` Martin K. Petersen
2016-06-22 12:51 ` Mauricio Faria de Oliveira
2016-06-01 20:43 ` [PATCH 2/2] lpfc: add option for lpfc_fcp_io_sched (LPFC_FCP_SCHED_BY_CPU_CORE) Mauricio Faria de Oliveira
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=57697C71.3060109@linux.vnet.ibm.com \
--to=mauricfo@linux.vnet.ibm.com \
--cc=dick.kennedy@broadcom.com \
--cc=hch@infradead.org \
--cc=james.smart@broadcom.com \
--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 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.