From: Bjorn Helgaas <helgaas@kernel.org>
To: Sinan Kaya <okaya@codeaurora.org>
Cc: linux-pci@vger.kernel.org, timur@codeaurora.org,
cov@codeaurora.org, vikrams@codeaurora.org,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: enable extended tags support for PCIe endpoints
Date: Fri, 11 Nov 2016 14:58:01 -0600 [thread overview]
Message-ID: <20161111205801.GC9868@bhelgaas-glaptop.roam.corp.google.com> (raw)
In-Reply-To: <420a9a23-79f8-41d8-c44f-b53f5000c957@codeaurora.org>
On Thu, Nov 10, 2016 at 01:35:41PM -0500, Sinan Kaya wrote:
> On 9/24/2016 10:10 PM, Sinan Kaya wrote:
> > Each PCIe device can issue up to 32 transactions at a time by default.
> > Each transaction is tracked by a tag number on the bus. 32 outstanding
> > transactions is not enough for some performance critical applications
> > especially when a lot of small sized frames are transmitted.
> >
> > Extended tags support increases this number to 256. Devices not
> > supporting extended tags tie-off this field to 0. According to ECN, it
> > is safe to enable this feature for all PCIe endpoints.
> >
> > Signed-off-by: Sinan Kaya <okaya@codeaurora.org>
> > ---
> > drivers/pci/probe.c | 7 +++++++
> > 1 file changed, 7 insertions(+)
> >
> > diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
> > index 93f280d..2424f38 100644
> > --- a/drivers/pci/probe.c
> > +++ b/drivers/pci/probe.c
> > @@ -1505,12 +1505,19 @@ static void program_hpp_type2(struct pci_dev *dev, struct hpp_type2 *hpp)
> > */
> > }
> >
> > +static int pci_configure_extended_tags(struct pci_dev *dev)
> > +{
>
> I should have checked the capability here before trying to enable it.
> I'll post a follow up patch on this.
>
> Is there any other feedback?
If this were completely safe to enable for every device that supported
it, why would there be an enable bit in Device Control?
I don't know anything about extended tags, but it worries me a little
when there's a "go-fast" switch and no explanation about when and why
we might need to go slow.
> > + return pcie_capability_set_word(dev, PCI_EXP_DEVCTL,
> > + PCI_EXP_DEVCTL_EXT_TAG);
> > +}
> > +
> > static void pci_configure_device(struct pci_dev *dev)
> > {
> > struct hotplug_params hpp;
> > int ret;
> >
> > pci_configure_mps(dev);
> > + pci_configure_extended_tags(dev);
> >
> > memset(&hpp, 0, sizeof(hpp));
> > ret = pci_get_hp_params(dev, &hpp);
> >
>
>
> --
> Sinan Kaya
> Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
> Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-11-11 20:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-25 2:10 Sinan Kaya
2016-11-10 18:35 ` Sinan Kaya
2016-11-11 20:58 ` Bjorn Helgaas [this message]
2016-11-12 1:11 ` Sinan Kaya
2017-01-25 17:49 ` Sinan Kaya
2017-01-25 18:33 ` Sinan Kaya
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=20161111205801.GC9868@bhelgaas-glaptop.roam.corp.google.com \
--to=helgaas@kernel.org \
--cc=cov@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=okaya@codeaurora.org \
--cc=timur@codeaurora.org \
--cc=vikrams@codeaurora.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
all inboxes | Powered by JetHome®