From: Lonnie Abelbeck <lists@lonnie.abelbeck.com>
To: Ryan Whelan <rcwhelan@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Wireguard Bug?
Date: Sun, 12 May 2019 18:02:33 -0500 [thread overview]
Message-ID: <398CDA20-DD9E-4434-AB16-D57A46B6E658@lonnie.abelbeck.com> (raw)
In-Reply-To: <CAM3m09Q3LCCFRJEe6J1UO0mtTiuVOYEiiyhEJJppDnuDnZZTwA@mail.gmail.com>
> On May 12, 2019, at 8:44 AM, Ryan Whelan <rcwhelan@gmail.com> wrote:
>
> I am building a system which coordinates the meshing of wireguard devices. Currently, all the devices are running on an embedded platform (AMD Geode LX500) and works as expected. However, when introducing a 64bit KVM host for testing, all the 32bit hosts running on the Geode platform, report the following warning and drop offline temporarily. The CPU usage on KVM host spikes and all the CPU time is spent on the kernel threads servicing the WG interfaces.
>
> I'm using kernel 4.19.41 and have seen the issue with both the last WG snapshot as well building from master.
Hi Ryan,
Did you mean "AMD Geode LX800 @500 MHz" ? (ex. ALIX/net5501)
If so, I have a couple of those using kernel 3.16.64 (i586) mixed with 3.16.64 (x86_64), and WG works well between them, no issues like you reported. iperf3 over WG runs at 23.8 Mbits/sec.
Lonnie
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-05-12 23:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-12 13:44 Wireguard Bug? Ryan Whelan
2019-05-12 15:41 ` Jason A. Donenfeld
2019-05-12 23:02 ` Lonnie Abelbeck [this message]
2019-06-14 11:56 ` Jason A. Donenfeld
2019-05-17 6:34 WireGuard Bug? . .
2019-05-18 17:03 ` Lucian Cristian
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=398CDA20-DD9E-4434-AB16-D57A46B6E658@lonnie.abelbeck.com \
--to=lists@lonnie.abelbeck.com \
--cc=rcwhelan@gmail.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).