Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Lonnie Abelbeck <lists@lonnie.abelbeck.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [ANNOUNCE] WireGuard Snapshot `0.0.20180620` Available
Date: Wed, 20 Jun 2018 17:37:20 -0500	[thread overview]
Message-ID: <981DB695-E660-431D-B5E9-ABD2D1352F9F@lonnie.abelbeck.com> (raw)
In-Reply-To: <CAHmME9r+uOOT_50zG3XQwB79reOhFBysE04=3=btubVQMdbuyQ@mail.gmail.com>


> On Jun 20, 2018, at 4:24 PM, Jason A. Donenfeld <Jason@zx2c4.com> =
wrote:
>=20
> Hey Lonnie,
>=20
> Thanks for letting me know. Can you tell me if this patch --
> https://=D7=90.cc/GJpT3gVY -- brings the performance back up? And if =
that
> works, can you then try each of those three fragments separate to see
> which one has an actual effect (or perhaps all do).
>=20
> Jason

Hunk #1 only does the trick, though performance is ever so slightly =
slower than before overall.

Is this issue because our project uses CONFIG_PREEMPT=3Dy ?

Data below.

Lonnie

-- 0.0.20180531 reference --
[SUM]   0.00-30.00  sec  2.65 GBytes   758 Mbits/sec  571             =
sender
[SUM]   0.00-30.02  sec  2.64 GBytes   756 Mbits/sec                  =
receiver

-- full patch --  hunk #1, #2 and #3
[SUM]   0.00-30.00  sec  2.53 GBytes   724 Mbits/sec  921             =
sender
[SUM]   0.00-30.01  sec  2.52 GBytes   722 Mbits/sec                  =
receiver

-- hunk #1 only --
[SUM]   0.00-30.00  sec  2.57 GBytes   735 Mbits/sec  807             =
sender
[SUM]   0.00-30.01  sec  2.56 GBytes   733 Mbits/sec                  =
receiver

-- hunk #2 only --
[SUM]   0.00-30.00  sec  1.52 GBytes   434 Mbits/sec   91             =
sender
[SUM]   0.00-30.02  sec  1.51 GBytes   433 Mbits/sec                  =
receiver

-- hunk #3 only --
[SUM]   0.00-30.00  sec  1.51 GBytes   432 Mbits/sec  330             =
sender
[SUM]   0.00-30.03  sec  1.50 GBytes   430 Mbits/sec                  =
receiver

  reply	other threads:[~2018-06-20 22:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-20 19:19 Jason A. Donenfeld
2018-06-20 20:11 ` Lonnie Abelbeck
2018-06-20 20:33   ` Matthias Urlichs
2018-06-20 21:24   ` Jason A. Donenfeld
2018-06-20 22:37     ` Lonnie Abelbeck [this message]
2018-06-20 23:47       ` Jason A. Donenfeld
2018-06-21  0:22         ` Lonnie Abelbeck
2018-06-21 13:51           ` 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=981DB695-E660-431D-B5E9-ABD2D1352F9F@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).