From: Roman Mamedov <rm@romanrm.net>
To: Lonnie Abelbeck <lists@lonnie.abelbeck.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: receive: use gro call instead of plain call
Date: Fri, 13 Jul 2018 21:15:26 +0500 [thread overview]
Message-ID: <20180713211526.5ead23b8@natsu> (raw)
In-Reply-To: <F0797C8C-D288-4531-A21F-4FD38764544A@lonnie.abelbeck.com>
On Fri, 13 Jul 2018 08:49:45 -0500
Lonnie Abelbeck <lists@lonnie.abelbeck.com> wrote:
> 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.
Yes I'm also seeing about 20% higher performance with this patch (from 1.3-1.4
to 1.6 Gbit on same-host VMs). This is awesome!
...and... if I switch TCP Congestion Control from bbr to illinois on sender, I
now get 2.0 Gbit. WTF. :)
Lonnie, which one do you use on your hosts? Try with illinois (it was the best
choice among all of them from my tests before bbr) and bbr (this one tends to
get a bit lower speeds overall, but ramps up so much faster at the start).
--
With respect,
Roman
next prev parent reply other threads:[~2018-07-13 16:07 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 [this message]
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=20180713211526.5ead23b8@natsu \
--to=rm@romanrm.net \
--cc=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.