From: Anuj Gupta <anuj20.g@samsung.com>
To: hkallweit1@gmail.com, davem@davemloft.net
Cc: holger@applied-asynchrony.com, kai.heng.feng@canonical.com,
simon.horman@corigine.com, nic_swsd@realtek.com,
netdev@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: Performance Regression due to ASPM disable patch
Date: Wed, 12 Jul 2023 21:25:21 +0530 [thread overview]
Message-ID: <20230712155052.GA946@green245> (raw)
In-Reply-To: CGME20230712155834epcas5p1140d90c8a0a181930956622728c4dd89@epcas5p1.samsung.com
[-- Attachment #1: Type: text/plain, Size: 1286 bytes --]
Hi,
I see a performance regression for read/write workloads on our NVMe over
fabrics using TCP as transport setup.
IOPS drop by 23% for 4k-randread [1] and by 18% for 4k-randwrite [2].
I bisected and found that the commit
e1ed3e4d91112027b90c7ee61479141b3f948e6a ("r8169: disable ASPM during
NAPI poll") is the trigger.
When I revert this commit, the performance drop goes away.
The target machine uses a realtek ethernet controller -
root@testpc:/home/test# lspci | grep -i eth
29:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Device 2600
(rev 21)
2a:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Killer
E3000 2.5GbE Controller (rev 03)
I tried to disable aspm by passing "pcie_aspm=off" as boot parameter and
by setting pcie aspm policy to performance. But it didn't improve the
performance.
I wonder if this is already known, and something different should be
done to handle the original issue?
[1] fio randread
fio -direct=1 -iodepth=1 -rw=randread -ioengine=psync -bs=4k -numjobs=1
-runtime=30 -group_reporting -filename=/dev/nvme1n1 -name=psync_read
-output=psync_read
[2] fio randwrite
fio -direct=1 -iodepth=1 -rw=randwrite -ioengine=psync -bs=4k -numjobs=1
-runtime=30 -group_reporting -filename=/dev/nvme1n1 -name=psync_read
-output=psync_write
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next parent reply other threads:[~2023-07-12 18:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230712155834epcas5p1140d90c8a0a181930956622728c4dd89@epcas5p1.samsung.com>
2023-07-12 15:55 ` Anuj Gupta [this message]
2023-07-13 5:59 ` Performance Regression due to ASPM disable patch Heiner Kallweit
2023-07-13 12:49 ` Anuj Gupta
2023-07-13 12:37 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-07-25 13:43 ` Linux regression tracking #update (Thorsten Leemhuis)
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=20230712155052.GA946@green245 \
--to=anuj20.g@samsung.com \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=holger@applied-asynchrony.com \
--cc=kai.heng.feng@canonical.com \
--cc=linux-nvme@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=simon.horman@corigine.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;
as well as URLs for NNTP newsgroup(s).