From: Bjorn Helgaas <helgaas@kernel.org>
To: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
Cc: Bean Huo <beanhuo@iokpp.de>,
bhelgaas@google.com, schnelle@linux.ibm.com,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Bean Huo <beanhuo@micron.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v2] PCI: Increase maximum PCIe physical function number to 7 for non-ARI devices
Date: Fri, 16 Feb 2024 16:41:09 -0600 [thread overview]
Message-ID: <20240216224109.GA1359930@bhelgaas> (raw)
In-Reply-To: <4858e202-6097-493a-8405-86d3e8e17c83@linux.intel.com>
On Fri, Feb 16, 2024 at 02:26:47PM -0800, Kuppuswamy Sathyanarayanan wrote:
>
> On 2/16/24 11:01 AM, Bean Huo wrote:
> > From: Bean Huo <beanhuo@micron.com>
> >
> > The PCIe specification allows up to 8 Physical Functions (PFs) per endpoint
> > when ARI (Alternative Routing-ID Interpretation) is not supported. Previously,
> > our implementation erroneously limited the maximum number of PFs to 7 for
> > endpoints without ARI support.
> I would quote specification reference here, like below:
>
> As per PCIe specification r6.2, sec titled "Alternative Routing-ID
> Interpretation (ARI)", up to 8 [fn # 0..7] functions are allowed in
> an non ARI capable device.
That's fine, just know that I silently convert citations like that
to "PCIe r6.2, sec 6.13" because I don't like having to grep for the
text ;)
Bjorn
next prev parent reply other threads:[~2024-02-16 22:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 19:01 [PATCH v2] PCI: Increase maximum PCIe physical function number to 7 for non-ARI devices Bean Huo
2024-02-16 22:26 ` Kuppuswamy Sathyanarayanan
2024-02-16 22:41 ` Bjorn Helgaas [this message]
2024-02-19 10:50 ` Bean Huo
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=20240216224109.GA1359930@bhelgaas \
--to=helgaas@kernel.org \
--cc=beanhuo@iokpp.de \
--cc=beanhuo@micron.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=schnelle@linux.ibm.com \
--cc=stable@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).