From: Yijing Wang <wangyijing@huawei.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Rob Landley <rob@landley.net>,
Bjorn Helgaas <bhelgaas@google.com>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Jon Mason <jdmason@kudzu.us>,
<linux-pci@vger.kernel.org>,
Andrew Murray <andrew.murray@arm.com>,
Hanjun Guo <guohanjun@huawei.com>, <jiang.liu@huawei.com>
Subject: Re: [Update][PATCH] PCI: Document PCIE BUS MPS parameters
Date: Thu, 24 Jan 2013 09:55:48 +0800 [thread overview]
Message-ID: <510094A4.3040806@huawei.com> (raw)
In-Reply-To: <510074C7.6090203@infradead.org>
Hi Randy,
Thanks for your review and comments! please refer to inlined comments below.
On 2013/1/24 7:39, Randy Dunlap wrote:
> On 01/23/13 04:28, Yijing Wang wrote:
>> Document PCIE BUS MPS parameters pcie_bus_tune_off, pcie_bus_safe,
>> pcie_bus_peer2peer, pcie_bus_perf into Documentation/kernel-parameters.txt.
>> These parameters were introduced by Jon Mason <mason@myri.com> at
>> commit 5f39e6705 and commit b03e7495a8. Document these into
>> kernel-parameters.txt can help users to understand and use the parameters.
>>
>> Signed-off-by: Yijing Wang <wangyijing@huawei.com>
>> ---
>> Documentation/kernel-parameters.txt | 15 +++++++++++++++
>> 1 files changed, 15 insertions(+), 0 deletions(-)
>>
>> diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
>> index 363e348..1fb269b 100644
>> --- a/Documentation/kernel-parameters.txt
>> +++ b/Documentation/kernel-parameters.txt
>> @@ -2227,6 +2227,21 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
>> This sorting is done to get a device
>> order compatible with older (<= 2.4) kernels.
>> nobfsort Don't sort PCI devices into breadth-first order.
>> + pcie_bus_tune_off Disable PCI-E MPS turning and using
>> + the BIOS configured MPS defaults.
>
> BIOS-configured
Will update it.
>
>> + pcie_bus_safe Use the smallest common denominator MPS
>> + of the entire tree below a root complex for every device
>> + on that fabric. Can avoid inconsistent mps problem caused
>
> s/mps/MPS/
> i.e., use "MPS" consistently.
Will use mps consistently.
>
>> + by hotplug.
>> + pcie_bus_perf Configure pcie device MPS to the largest allowable
>> + MPS based on its parent bus. And also set MRRS to the
>
> "And also" is redundant. Just say Also.
Ok.
>
> What is (are) MRRS?
MRRS is "Max Read Request Size" and MPS is "Max Payload Size".
Need use "Max Read Request Size" instead of MRRS ?
>
>> + largest supported value but cannot be configured larger
>> + than the MPS the device or the bus can support for Max
>> + performance.
>> + pcie_bus_peer2peer Make the system wide MPS the smallest
>
> system-wide
Will update it.
>
>> + possible value (128B).This configuration could prevent it
>
> ^ Space before "This"
>
Thanks for reminder.
>> + from working by having the MPS on one root port different
>> + than the MPS on another.
>> cbiosize=nn[KMG] The fixed amount of bus space which is
>> reserved for the CardBus bridge's IO window.
>> The default value is 256 bytes.
>>
>
>
--
Thanks!
Yijing
next prev parent reply other threads:[~2013-01-24 1:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 12:28 [Update][PATCH] PCI: Document PCIE BUS MPS parameters Yijing Wang
2013-01-23 23:39 ` Randy Dunlap
2013-01-24 1:55 ` Yijing Wang [this message]
2013-01-24 2:02 ` Randy Dunlap
2013-01-24 2:20 ` Yijing Wang
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=510094A4.3040806@huawei.com \
--to=wangyijing@huawei.com \
--cc=andrew.murray@arm.com \
--cc=bhelgaas@google.com \
--cc=guohanjun@huawei.com \
--cc=jdmason@kudzu.us \
--cc=jiang.liu@huawei.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=rob@landley.net \
/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