From: Roman Mamedov <rm@romanrm.net>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [ANNOUNCE] WireGuard Snapshot `0.0.20180708` Available
Date: Tue, 10 Jul 2018 23:37:22 +0500 [thread overview]
Message-ID: <20180710233722.31d6b060@natsu> (raw)
In-Reply-To: <20180710205729.645bc734@natsu>
On Tue, 10 Jul 2018 20:57:29 +0500
Roman Mamedov <rm@romanrm.net> wrote:
> I'll probably test again without simd_relax
Somehow it's now noticeably worse without those. Even got some dips below
1 Gbit/s which I have never seen before, and the overall speed is lower.
--
With respect,
Roman
next prev parent reply other threads:[~2018-07-10 18:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-08 16:52 [ANNOUNCE] WireGuard Snapshot `0.0.20180708` Available Jason A. Donenfeld
2018-07-10 14:54 ` Roman Mamedov
2018-07-10 14:57 ` Jason A. Donenfeld
2018-07-10 15:57 ` Roman Mamedov
2018-07-10 18:37 ` Roman Mamedov [this message]
2018-07-10 18:38 ` Jason A. Donenfeld
2018-07-10 19:07 ` Roman Mamedov
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=20180710233722.31d6b060@natsu \
--to=rm@romanrm.net \
--cc=Jason@zx2c4.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).