From: Sinan Kaya <okaya@codeaurora.org>
To: unlisted-recipients:; (no To-header on input)
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] PCI: enable extended tags support for PCIe devices
Date: Fri, 20 Jan 2017 09:36:45 -0500 [thread overview]
Message-ID: <1214d229-0f0c-d9fd-3d25-39a6e257a36b@codeaurora.org> (raw)
In-Reply-To: <1484921814-8511-1-git-send-email-okaya@codeaurora.org>
On 1/20/2017 9:16 AM, Sinan Kaya wrote:
> Each PCIe device can issue up to 32 transactions at a time by default.
> This limitation is historically coming from PCI. Each transaction is
> tracked by a tag number on the bus. 2.2.6.2. Transaction Descriptor
> – Transaction ID Field section of the PCIe 3.1 specification describes
> extended tags.
>
Apologies for the spam, no idea what happened. I need to review my publish scripts.
next prev parent reply other threads:[~2017-01-20 14:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 14:16 [PATCH V2] PCI: enable extended tags support for PCIe devices Sinan Kaya
2017-01-20 14:36 ` Sinan Kaya [this message]
2017-02-09 23:33 ` Bjorn Helgaas
2017-02-09 23:40 ` Sinan Kaya
-- strict thread matches above, loose matches on Subject: below --
2017-01-20 14:19 Sinan Kaya
2017-01-20 14:20 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=1214d229-0f0c-d9fd-3d25-39a6e257a36b@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=bhelgaas@google.com \
--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).