From: Lonnie Abelbeck <lists@lonnie.abelbeck.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: receive: use gro call instead of plain call
Date: Fri, 13 Jul 2018 08:49:45 -0500 [thread overview]
Message-ID: <F0797C8C-D288-4531-A21F-4FD38764544A@lonnie.abelbeck.com> (raw)
In-Reply-To: <580E3DE0-4D06-46C5-A972-96C1F687A7B7@abelbeck.com>
For certain lower-end x86 boxes I test, I noticed WG 0.0.20180708 w/NAPI =
actually slowed down receive performance.
Jason recently added "receive: use gro call instead of plain call" [1] =
commit, which made a big performance improvement.
Here is a test on a PC Engines APU2 ...
pbx4: AMD GX-412TC SOC (1 GHz, 4-core)
Ethernet controller: Intel Corporation I210
pbx: Intel(R) Core(TM) i3-6100U CPU @ 2.30GHz
Ethernet controller: Intel Corporation I211
# uname -a
Linux pbx4 3.16.57-astlinux #1 SMP PREEMPT Mon Jul 9 17:25:31 CDT 2018 =
x86_64 GNU/Linux
pbx ~ # iperf3 -s
pbx4 ~ # iperf3 -c 10.4.0.10 -P2 -R
-- 0.0.20180625 --
[SUM] 0.00-10.04 sec 466 MBytes 390 Mbits/sec 162 =
sender
[SUM] 0.00-10.00 sec 463 MBytes 389 Mbits/sec =
receiver
-- 0.0.20180708 --
[SUM] 0.00-10.04 sec 301 MBytes 252 Mbits/sec 30 =
sender
[SUM] 0.00-10.00 sec 300 MBytes 251 Mbits/sec =
receiver
-- 0.0.20180708 w/napi_gro_receive patch --
[SUM] 0.00-10.04 sec 596 MBytes 498 Mbits/sec 92 =
sender
[SUM] 0.00-10.00 sec 594 MBytes 498 Mbits/sec =
receiver
--
Kudos Jason !
Lonnie
[1] =
https://git.zx2c4.com/WireGuard/commit/?id=3D95951af7249912a4356b9a03cf3ad=
dc7e3f8f724=
next parent reply other threads:[~2018-07-13 13:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHmME9rP8fE7U9VxLauQ_Ee-w6ox-DAAFkvAOjx52bxGT58w4w@mail.gmail.com>
[not found] ` <580E3DE0-4D06-46C5-A972-96C1F687A7B7@abelbeck.com>
2018-07-13 13:49 ` Lonnie Abelbeck [this message]
2018-07-13 16:15 ` Roman Mamedov
2018-07-13 18:06 ` Lonnie Abelbeck
2018-07-13 18:27 ` Jason A. Donenfeld
2018-07-13 21:17 ` Lonnie Abelbeck
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=F0797C8C-D288-4531-A21F-4FD38764544A@lonnie.abelbeck.com \
--to=lists@lonnie.abelbeck.com \
--cc=wireguard@lists.zx2c4.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).