From: Lonnie Abelbeck <lists@lonnie.abelbeck.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: receive: use gro call instead of plain call
Date: Fri, 13 Jul 2018 16:17:18 -0500 [thread overview]
Message-ID: <5B4A607E-C728-4D5D-8214-4D84B40B5B23@lonnie.abelbeck.com> (raw)
In-Reply-To: <CAHmME9rUf87VA2u0Nqh2jQ=_D2aAug1z4vYz6ctHXznarkA0KQ@mail.gmail.com>
> On Jul 13, 2018, at 1:27 PM, Jason A. Donenfeld <Jason@zx2c4.com> =
wrote:
>=20
> Hey Lonnie,
>=20
> Wow, thanks for benching that (and watching the git repo for the
> experiment-of-the-day). This performance increase certainly exceeds my
> expectations; I'm quite pleased it's working so well.
Another huge improvement ...
pbx3: Intel(R) Celeron(R) CPU N2930 @ 1.83GHz
Ethernet controller: Intel Corporation I211
pbx: Intel(R) Core(TM) i3-6100U CPU @ 2.30GHz
Ethernet controller: Intel Corporation I211
pbx ~ # iperf3 -s
pbx3 ~ # iperf3 -c 10.4.0.10 -P2 -R
-- 0.0.20180625 --
[SUM] 0.00-10.03 sec 940 MBytes 786 Mbits/sec 251 =
sender
[SUM] 0.00-10.00 sec 933 MBytes 782 Mbits/sec =
receiver
-- 0.0.20180708 --
[SUM] 0.00-10.05 sec 730 MBytes 609 Mbits/sec 186 =
sender
[SUM] 0.00-10.01 sec 726 MBytes 608 Mbits/sec =
receiver
-- 0.0.20180708 w/napi_gro_receive patch --
[SUM] 0.00-10.04 sec 973 MBytes 813 Mbits/sec 289 =
sender
[SUM] 0.00-10.00 sec 969 MBytes 813 Mbits/sec =
receiver
--
Lonnie
prev parent reply other threads:[~2018-07-13 21:09 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 ` receive: use gro call instead of plain call Lonnie Abelbeck
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 [this message]
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=5B4A607E-C728-4D5D-8214-4D84B40B5B23@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.