From: Roland Dreier <rdreier@cisco.com>
To: Alex Chiang <achiang@hp.com>
Cc: "Zhao\, Yu" <yu.zhao@intel.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
linux-pci@vger.kernel.org, Randy Dunlap <randy.dunlap@oracle.com>,
Greg KH <greg@kroah.com>,
Grant Grundler <grundler@parisc-linux.org>,
Matthew Wilcox <matthew@wil.cx>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
virtualization@lists.linux-foundation.org,
xen-devel@lists.xensource.com
Subject: Re: [PATCH 2/4 v2] PCI: support ARI capability
Date: Mon, 01 Sep 2008 08:50:23 -0700 [thread overview]
Message-ID: <ada3akjj268.fsf@cisco.com> (raw)
In-Reply-To: <20080901152734.GC16796@ldl.fc.hp.com> (Alex Chiang's message of "Mon, 1 Sep 2008 09:27:34 -0600")
> > +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 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.
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?
- R.
next prev parent reply other threads:[~2008-09-01 15:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-01 11:20 [PATCH 2/4 v2] PCI: support ARI capability Zhao, Yu
2008-09-01 15:27 ` Alex Chiang
2008-09-01 15:50 ` Roland Dreier [this message]
2008-09-10 7:48 ` Zhao, Yu
2008-09-10 18:42 ` Roland Dreier
2008-09-10 20:07 ` Matthew Wilcox
2008-09-10 7:35 ` Zhao, Yu
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=ada3akjj268.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=achiang@hp.com \
--cc=greg@kroah.com \
--cc=grundler@parisc-linux.org \
--cc=jbarnes@virtuousgeek.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=randy.dunlap@oracle.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xen-devel@lists.xensource.com \
--cc=yu.zhao@intel.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