From: Jon Mason <jon.mason@intel.com>
To: Yijing Wang <wangyijing@huawei.com>
Cc: Hanjun Guo <guohanjun@huawei.com>,
jiang.liu@huawei.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 10/16] ntb: clean up unnecessary MSI/MSI-X capability find
Date: Thu, 8 Aug 2013 09:42:36 -0700 [thread overview]
Message-ID: <20130808164235.GB21762@jonmason-lab> (raw)
In-Reply-To: <1375967374-28704-1-git-send-email-wangyijing@huawei.com>
On Thu, Aug 08, 2013 at 09:09:34PM +0800, Yijing Wang wrote:
> PCI core will initialize device MSI/MSI-X capability in
> pci_msi_init_pci_dev(). So device driver should use
> pci_dev->msi_cap/msix_cap to determine whether the device
> support MSI/MSI-X instead of using
> pci_find_capability(pci_dev, PCI_CAP_ID_MSI/MSIX).
> Access to PCIe device config space again will consume more time.
>
> Signed-off-by: Yijing Wang <wangyijing@huawei.com>
> Cc: Jon Mason <jon.mason@intel.com>
Acked-by: Jon Mason <jon.mason@intel.com>
> Cc: linux-kernel@vger.kernel.org
> ---
> drivers/ntb/ntb_hw.c | 7 +++----
> 1 files changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/ntb/ntb_hw.c b/drivers/ntb/ntb_hw.c
> index 2dacd19..090d1b2 100644
> --- a/drivers/ntb/ntb_hw.c
> +++ b/drivers/ntb/ntb_hw.c
> @@ -758,16 +758,15 @@ static int ntb_setup_msix(struct ntb_device *ndev)
> struct pci_dev *pdev = ndev->pdev;
> struct msix_entry *msix;
> int msix_entries;
> - int rc, i, pos;
> + int rc, i;
> u16 val;
>
> - pos = pci_find_capability(pdev, PCI_CAP_ID_MSIX);
> - if (!pos) {
> + if (!pdev->msix_cap) {
> rc = -EIO;
> goto err;
> }
>
> - rc = pci_read_config_word(pdev, pos + PCI_MSIX_FLAGS, &val);
> + rc = pci_read_config_word(pdev, pdev->msix_cap + PCI_MSIX_FLAGS, &val);
> if (rc)
> goto err;
>
> --
> 1.7.1
>
>
prev parent reply other threads:[~2013-08-08 16:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 13:09 Yijing Wang
2013-08-08 16:42 ` Jon Mason [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=20130808164235.GB21762@jonmason-lab \
--to=jon.mason@intel.com \
--cc=guohanjun@huawei.com \
--cc=jiang.liu@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wangyijing@huawei.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
all inboxes | Powered by JetHome®