linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-pci@vger.kernel.org, agordeev@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: pci: automatic interrupt affinity for MSI/MSI-X capable devices V2
Date: Thu, 21 Jul 2016 16:06:42 -0500	[thread overview]
Message-ID: <20160721210642.GB11888@localhost> (raw)
In-Reply-To: <1468315218-20490-1-git-send-email-hch@lst.de>

On Tue, Jul 12, 2016 at 06:20:13PM +0900, Christoph Hellwig wrote:
> This series adds a new set of functions that transparently use the right
> type of interrupt (MSI-X, MSI, legacy interrupt line) for a PCI device,
> and if multiple vectors are supported automatically spreads the irq
> routing to different CPUs.  This will allow the block layer (and hopefully
> other consumers in the future) to use this information for mapping
> queues to fit the interrupt affinity.
> 
> For the last patche to work you need to merge the irq/for-block branch of
> 
>    https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
> 
> first.
> 
> There also is a git tree available at:
> 
>    git://git.infradead.org/users/hch/block.git pci-irq-spreading
> 
> Gitweb:
> 
>    http://git.infradead.org/users/hch/block.git/shortlog/refs/heads/pci-irq-spreading
> 
> Changes since V1
>  - change return values for the minmum vector check
>  - improve the documentation
> 
> Changes since automatic interrupt affinity for MSI/MSI-X capable devices V3:
>  - add PCI_IRQ_NOLEGACY flag
>  - various error code fixes
>  - reuse the pci_enable_msi(x)_range code instead of duplicating it
>  - don't allocate msix_entry structures for the MSI-X case

I merged the irq/for-block branch, applied this series, and added
Alexander's Reviewed-by to the patches that didn't have it already.

As far as the if/return/else construct:

  if (x)
    return y;
  else if (z)
    ...

I removed the "else" in the other occurrences so the style is
consistently:

  if (x)
    return y;
  if (z)
    ...

This is all on my pci/msi-affinity branch for v4.8.

Thanks for all the work; I think this is a very nice change, and it's
great that all the documentation is updated as well.

Bjorn

  parent reply	other threads:[~2016-07-21 21:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-12  9:20 pci: automatic interrupt affinity for MSI/MSI-X capable devices V2 Christoph Hellwig
2016-07-12  9:20 ` [PATCH 1/5] pci: add a pci_msix_desc_addr helper Christoph Hellwig
2016-07-12 12:59   ` Alexander Gordeev
2016-07-12  9:20 ` [PATCH 2/5] pci: switch msix_program_entries to use pci_msix_desc_addr Christoph Hellwig
2016-07-12 12:59   ` Alexander Gordeev
2016-07-12  9:20 ` [PATCH 3/5] pci: make the entries argument to pci_enable_msix optional Christoph Hellwig
2016-07-12  9:20 ` [PATCH 4/5] pci: Provide sensible irq vector alloc/free routines Christoph Hellwig
2016-07-12 12:58   ` Alexander Gordeev
2016-07-12  9:20 ` [PATCH 5/5] pci: spread interrupt vectors in pci_alloc_irq_vectors Christoph Hellwig
2016-07-12 12:57   ` Alexander Gordeev
2016-07-21 21:06 ` Bjorn Helgaas [this message]
2016-07-21 21:10   ` pci: automatic interrupt affinity for MSI/MSI-X capable devices V2 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=20160721210642.GB11888@localhost \
    --to=helgaas@kernel.org \
    --cc=agordeev@redhat.com \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@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;
as well as URLs for NNTP newsgroup(s).