From: Bjorn Helgaas <bhelgaas@google.com>
To: Gavin Shan <shangw@linux.vnet.ibm.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH v3 0/5] Retrieve MSI/MSIX cap struct for once on setup
Date: Mon, 22 Apr 2013 17:11:37 -0600 [thread overview]
Message-ID: <CAErSpo5hseSsR65cUd5ivVf=pC_x25HSHQHMH+MXbA3fOZC-wQ@mail.gmail.com> (raw)
In-Reply-To: <5167564e.c628320a.6610.1710SMTPIN_ADDED_BROKEN@mx.google.com>
On Thu, Apr 11, 2013 at 6:33 PM, Gavin Shan <shangw@linux.vnet.ibm.com> wrote:
> On Fri, Apr 05, 2013 at 11:01:18AM +0800, Gavin Shan wrote:
>>On Fri, Apr 05, 2013 at 10:54:29AM +0800, Gavin Shan wrote:
>>
>>The subject should be "[0/4]" instead of "[0/5]". Forgot to change
>>that accordingly. Sorry for the confusion ;-)
>>
>
> Bjorn, did you get change taking a look on this? Please let me know
> if you have more comments :-)
I did look at it; it looks good, and I made some more cleanups, which
I just posted as a "v4" series. Take a look and see if it makes sense
to you.
Bjorn
>>>While we setup MSI or MSI-X for specific PCI device, the address of
>>>MSI or MSI-X capability structure is figured out from the config
>>>space for multiple times. That's unnecessary and the patchset addresses
>>>that. With the patchset applied, the latency for MSI or MSI-X setup
>>>would be decreased hopefully.
>>>
>>>v2 -> v3:
>>> * Remove checking on MSI/MSI-X capability offset in msi_set_enable()
>>> and msix_set_enable(). Let the caller does the check
>>> * Using "u8" for MSI/MSI-X/PM capability
>>> * Let caller of pci_msi_check_device() checks MSI/MSI-X capability
>>> * Replace msi_control_reg() with "pos + PCI_MSI_FLAGS"
>>> * Merge [4/5] to [3/5]
>>>v1 -> v2:
>>> * Cache the MSI/MSI-X capability offset to pci_dev directly according
>>> to Bjorn's suggestion.
>>> * Rebase to 3.9.RC5
>>>
>>>---
>>>
>>>drivers/pci/msi.c | 110 +++++++++++++++++++++++----------------------------
>>>drivers/pci/msi.h | 1 -
>>>include/linux/pci.h | 4 +-
>>>3 files changed, 52 insertions(+), 63 deletions(-)
>>>
>>>Thanks,
>>>Gavin
>>>
>
prev parent reply other threads:[~2013-04-22 23:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 2:54 [PATCH v3 0/5] Retrieve MSI/MSIX cap struct for once on setup Gavin Shan
2013-04-05 2:54 ` [PATCH 1/4] PCI: Cache MSI/MSI-X cap in PCI device Gavin Shan
2013-04-05 2:54 ` [PATCH 2/4] PCI: Remove MSI/MSI-X cap check in pci_msi_check_device() Gavin Shan
2013-04-05 2:54 ` [PATCH 3/4] PCI: Use cached MSI cap while enabling MSI interrupts Gavin Shan
2013-04-05 2:54 ` [PATCH 4/4] PCI: Use cached MSI-X cap while enabling MSI-X Gavin Shan
[not found] ` <5167564e.c628320a.6610.1710SMTPIN_ADDED_BROKEN@mx.google.com>
2013-04-22 23:11 ` Bjorn Helgaas [this message]
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='CAErSpo5hseSsR65cUd5ivVf=pC_x25HSHQHMH+MXbA3fOZC-wQ@mail.gmail.com' \
--to=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=shangw@linux.vnet.ibm.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 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).