From: Sinan Kaya <okaya@codeaurora.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-pci@vger.kernel.org
Subject: Re: ECRC and Max Read Request Size
Date: Mon, 9 Nov 2015 19:43:11 -0500 [thread overview]
Message-ID: <56413D9F.5050902@codeaurora.org> (raw)
In-Reply-To: <20151109191517.GA4789@localhost>
On 11/9/2015 2:15 PM, Bjorn Helgaas wrote:
>> I talked to our performance team. They are saying that max read
>> >request does not gain you much compared to max payload size single
>> >direction but it helps tremendously if you are moving data forth and
>> >back between the card. I don't have real numbers though.
> I'm not enough of a hardware or performance person to visualize how
> MRRS makes a tremendous difference in this situation. Sample
> timelines comparing small vs. large MRRS would help everybody
> understand what's happening here.
>
> Bjorn
The LSI SAS 9211i card supports 4k maximum read request size. I manually
forced this to 4k instead of the maximum payload size of the platform on
both the host bridge and the endpoint.
I did a quick test with:
dd if=/dev/zero of=/dev/sda bs=1G count=1
It gave me %9 higher write performance.
--
Sinan Kaya
Qualcomm Technologies, Inc. on behalf of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a
Linux Foundation Collaborative Project
next prev parent reply other threads:[~2015-11-10 0:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 17:51 ECRC and Max Read Request Size Sinan Kaya
2015-11-06 17:22 ` Bjorn Helgaas
2015-11-06 17:54 ` Sinan Kaya
2015-11-07 0:11 ` Bjorn Helgaas
2015-11-07 3:39 ` Sinan Kaya
2015-11-09 19:47 ` Bjorn Helgaas
2015-11-10 0:09 ` Sinan Kaya
2015-11-09 19:15 ` Bjorn Helgaas
2015-11-10 0:43 ` Sinan Kaya [this message]
2015-11-08 17:20 ` Sinan Kaya
-- strict thread matches above, loose matches on Subject: below --
2015-10-26 18:42 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=56413D9F.5050902@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=helgaas@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).