On Wed, Sep 10, 2008 at 03:48:04PM +0800, Zhao, Yu wrote:
> >I agree with this improvement to the help text. But a further question
> >is whether ARI even merits its own user-visible config option. Is it
> >worth having yet another choice for users? When would someone want ARI
> >but not SR-IOV?
> ARI is an independent PCI Express extended capability. Multi-function
> devices supporting this capability may use it to track dependency
> between different functions and assign function group numbers to
> these functions.
> Another reason to keep this separated with SR-IOV is that after A
On Monday, September 01, 2008 11:50 PM, Roland Dreier wrote:
>To: Alex Chiang
>Cc: Zhao, Yu; Jesse Barnes; [EMAIL PROTECTED]; Randy Dunlap; Greg KH;
>Grant Grundler; Matthew Wilcox; [EMAIL PROTECTED];
>kvm@vger.kernel.org; [EMAIL PROTECTED];
>[EMAIL PROTECTED]
>Subject: Re:
On Monday, September 01, 2008 11:28 PM, Alex Chiang wrote:
>* Zhao, Yu <[EMAIL PROTECTED]>:
>> Support Alternative Routing-ID Interpretation (ARI), which increases the
>number of functions that can be supported by a PCIe endpoint. ARI is required
>by SR-IOV.
>>
>> PCI-SIG ARI specification can be f
> > +config PCI_ARI
> > + bool "PCI ARI support"
> > + depends on PCI
> > + default n
> > + help
> > +This enables PCI Alternative Routing-ID Interpretation.
>
> This Kconfig help text is a little weak. Why not include the text
> you've already written here:
>
> Support Al
* Zhao, Yu <[EMAIL PROTECTED]>:
> Support Alternative Routing-ID Interpretation (ARI), which increases the
> number of functions that can be supported by a PCIe endpoint. ARI is required
> by SR-IOV.
>
> PCI-SIG ARI specification can be found at
> http://www.pcisig.com/specifications/pciexpress
Support Alternative Routing-ID Interpretation (ARI), which increases the number
of functions that can be supported by a PCIe endpoint. ARI is required by
SR-IOV.
PCI-SIG ARI specification can be found at
http://www.pcisig.com/specifications/pciexpress/specifications/ECN-alt-rid-interpretation-0
