All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Smart <james.smart@broadcom.com>
To: Christoph Hellwig <hch@lst.de>
Cc: hare@suse.de, linux-scsi@vger.kernel.org
Subject: Re: use PCI layer IRQ affinity in lpfc
Date: Fri, 18 Nov 2016 08:21:35 -0800	[thread overview]
Message-ID: <96e879ef-3152-f133-b89d-ae3f2661a85e@broadcom.com> (raw)
In-Reply-To: <1479395693-5781-1-git-send-email-hch@lst.de>

Hi Christoph,

We had already done this work in the larger lpfc patch that had been 
posted for nvme work.

I'll look at separating out just the irq part and post a reply.

-- james


On 11/17/2016 7:14 AM, Christoph Hellwig wrote:
> This series has two patches: the first is a simple conversion of
> lpfc to use pci_alloc_irq_vectors.  The second is more interesting,
> and makes use of the PCI_IRQ_AFFINITY option to use the core interrupt
> affinity assignment that takes nodes into account and can be easily
> queried.  It also ensures we propagate this information to blk-mq
> to make sure the block layer queues are properly aligned to the
> interrupt vectors.
>
> Note that these patches require core IRQ changes from a stable
> branch in the tip tree to be pulled in first:
>
> 	git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq/for-block
>
> Also be aware that I don't have any lpfc hardware to actually test these.


  parent reply	other threads:[~2016-11-18 16:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-17 15:14 use PCI layer IRQ affinity in lpfc Christoph Hellwig
2016-11-17 15:14 ` [PATCH 1/2] lpfc: use pci_irq_alloc_vectors and pci_irq_free_vectors Christoph Hellwig
2016-11-17 15:14 ` [PATCH 2/2] lpfc: use PCI-layer irq affinity handling Christoph Hellwig
2016-11-18 13:13 ` use PCI layer IRQ affinity in lpfc Johannes Thumshirn
2016-11-18 13:22   ` Hannes Reinecke
2016-11-18 13:22   ` Christoph Hellwig
2016-11-18 13:25     ` Johannes Thumshirn
2016-11-18 14:20     ` Johannes Thumshirn
2016-11-18 16:21 ` James Smart [this message]
2016-11-21 14:06   ` Christoph Hellwig
2017-01-08 15:02     ` Christoph Hellwig

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=96e879ef-3152-f133-b89d-ae3f2661a85e@broadcom.com \
    --to=james.smart@broadcom.com \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --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.