From: Bjorn Helgaas <helgaas@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: tglx@linutronix.de, linux-block@vger.kernel.org,
linux-pci@vger.kernel.org, linux-nvme@lists.infradead.org,
linux-kernel@vger.kernel.org,
Alexander Gordeev <agordeev@redhat.com>
Subject: Re: [PATCH 6/8] pci: provide sensible irq vector alloc/free routines
Date: Tue, 3 May 2016 16:37:56 -0500 [thread overview]
Message-ID: <20160503213756.GA17170@localhost> (raw)
In-Reply-To: <20160503211945.GA25167@lst.de>
On Tue, May 03, 2016 at 11:19:46PM +0200, Christoph Hellwig wrote:
> Hi Bjorn,
>
> I've implemented your suggestion and I'm getting ready to send out
> a new version. One thing that came to mind is: do you prefer this
> code in irq.c or would you rather have it in msi.c? While it
> also has a legacy irq fallback most of it tied pretty closely to
> the msi.c code, so I wonder if we should group them together.
Good question. There isn't much in irq.c, and the interesting bits
are the MSI-related things, so maybe msi.c would make more sense.
Bjorn
WARNING: multiple messages have this Message-ID (diff)
From: helgaas@kernel.org (Bjorn Helgaas)
Subject: [PATCH 6/8] pci: provide sensible irq vector alloc/free routines
Date: Tue, 3 May 2016 16:37:56 -0500 [thread overview]
Message-ID: <20160503213756.GA17170@localhost> (raw)
In-Reply-To: <20160503211945.GA25167@lst.de>
On Tue, May 03, 2016@11:19:46PM +0200, Christoph Hellwig wrote:
> Hi Bjorn,
>
> I've implemented your suggestion and I'm getting ready to send out
> a new version. One thing that came to mind is: do you prefer this
> code in irq.c or would you rather have it in msi.c? While it
> also has a legacy irq fallback most of it tied pretty closely to
> the msi.c code, so I wonder if we should group them together.
Good question. There isn't much in irq.c, and the interesting bits
are the MSI-related things, so maybe msi.c would make more sense.
Bjorn
next prev parent reply other threads:[~2016-05-03 21:38 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-16 1:35 RFC: automatic interrupt affinity for MSI/MSI-X capable devices Christoph Hellwig
2016-04-16 1:35 ` Christoph Hellwig
2016-04-16 1:35 ` [PATCH 1/8] device: Add irq affinity hint cpumask pointer Christoph Hellwig
2016-04-16 1:35 ` Christoph Hellwig
2016-04-16 1:35 ` [PATCH 2/8] genirq: Make use of dev->irq_affinity Christoph Hellwig
2016-04-16 1:35 ` Christoph Hellwig
2016-04-16 1:35 ` [PATCH 3/8] genirq: add a helper spread an affinity mask for MSI/MSI-X vectors Christoph Hellwig
2016-04-16 1:35 ` Christoph Hellwig
2016-04-16 1:35 ` [PATCH 4/8] genirq: add a helper to program the pre-set affinity mask into the controller Christoph Hellwig
2016-04-16 1:35 ` Christoph Hellwig
2016-04-16 1:35 ` [PATCH 5/8] blk-mq: allow the driver to pass in an affinity mask Christoph Hellwig
2016-04-16 1:35 ` Christoph Hellwig
2016-04-16 1:35 ` [PATCH 6/8] pci: provide sensible irq vector alloc/free routines Christoph Hellwig
2016-04-16 1:35 ` Christoph Hellwig
2016-04-29 21:16 ` Bjorn Helgaas
2016-04-29 21:16 ` Bjorn Helgaas
2016-05-01 18:01 ` Christoph Hellwig
2016-05-01 18:01 ` Christoph Hellwig
2016-05-02 13:11 ` Bjorn Helgaas
2016-05-02 13:11 ` Bjorn Helgaas
2016-05-02 14:42 ` Christoph Hellwig
2016-05-02 14:42 ` Christoph Hellwig
2016-05-02 15:29 ` Bjorn Helgaas
2016-05-02 15:29 ` Bjorn Helgaas
2016-05-03 21:19 ` Christoph Hellwig
2016-05-03 21:19 ` Christoph Hellwig
2016-05-03 21:37 ` Bjorn Helgaas [this message]
2016-05-03 21:37 ` Bjorn Helgaas
2016-04-16 1:35 ` [PATCH 7/8] pci: spread interrupt vectors in pci_alloc_irq_vectors Christoph Hellwig
2016-04-16 1:35 ` Christoph Hellwig
2016-04-18 8:30 ` Thomas Gleixner
2016-04-18 8:30 ` Thomas Gleixner
2016-04-16 1:35 ` [PATCH 8/8] nvme: switch to use pci_alloc_irq_vectors Christoph Hellwig
2016-04-16 1:35 ` 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=20160503213756.GA17170@localhost \
--to=helgaas@kernel.org \
--cc=agordeev@redhat.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.