From: wangyijing <wangyijing@huawei.com>
To: <linux-pci@vger.kernel.org>
Cc: <jianghong011@huawei.com>, <wangyijing@huawei.com>
Subject: Question about cacheline size in PCIe SAS card
Date: Thu, 28 Jul 2016 16:15:31 +0800 [thread overview]
Message-ID: <5799BF23.2020902@huawei.com> (raw)
Hi all, we found a question about PCIe cacheline, the cacheline here is mean the
configure space register at offset 0x0C in type 0 and type 1 configure space header.
We did a hotplug in our platform for PCIe SAS controller, this sas controller has
SSD disks and the disk sector is 520 bytes. Defaultly, BIOS set cacheline size to
64bytes, we test the IO read(io size is 128k/256k), the bandwith is 6G.
After hotplug, the cacheline size in SAS controller changes to 0(default after #RST),
and we test the IO read again, the bandwith changes to 5.2G.
We Tested other SAS controller which is not 520 bytes sector, we didn't found this issue,
and I grep the PCI_CACHE_LINE_SIZE in kernel, I found most of code change the PCI_CACHE_LINE_SIZE
are device driver, like net, ata, and some arm pci controller.
In PCI 3.0 spec, I found there are descriptions about cacheline size releated to performance,
but in PCIe 3.0 spec, there is nothing related to cacheline size.
I wonder what's cacheline register roles in PCIe spec, how can we use it correctly ?
Thanks!
Yijing.
next reply other threads:[~2016-07-28 8:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 8:15 wangyijing [this message]
2016-07-28 18:43 ` Question about cacheline size in PCIe SAS card Bjorn Helgaas
2016-07-29 2:53 ` wangyijing
2016-07-29 12:41 ` Bjorn Helgaas
2016-07-30 1:49 ` wangyijing
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=5799BF23.2020902@huawei.com \
--to=wangyijing@huawei.com \
--cc=jianghong011@huawei.com \
--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).