From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: n3ph <n3ph@terminal21.de>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [WireGuard] OpenWRT/MIPS Improvements
Date: Sat, 12 Nov 2016 15:36:59 +0100 [thread overview]
Message-ID: <CAHmME9rdAOep+EUQDoK3nxBaM6VqrU99=v=LvrBhy5m46oOw6w@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9p08K4M-+qvRO1kJiTScj66QDmFofu6d6nNK6eANTnYZA@mail.gmail.com>
Hey folks,
Small update on the OOM issue. With LEDE devices that only have
32megs, if you run iperf3 on the device itself, eventually iperf3 will
use tons of memory in trying to use different sized buffers, that the
device will OOM and kill init. However, if you use packet forwarding
and put iperf3 on a different device -- more closely resembling the
actual workload of a router -- there is no OOM, and memory usage stays
stable overtime, indicating there isn't a memory leak or anything of
that nature in WireGuard. So, I think at this point WireGuard is quite
stable on LEDE.
Looking forward to hearing your feedback on the matter.
Regards,
Jason
prev parent reply other threads:[~2016-11-12 14:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-10 18:40 Jason A. Donenfeld
[not found] ` <20161111070445.GB10286@c3po>
2016-11-11 14:29 ` Jason A. Donenfeld
2016-11-12 14:36 ` Jason A. Donenfeld [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='CAHmME9rdAOep+EUQDoK3nxBaM6VqrU99=v=LvrBhy5m46oOw6w@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=n3ph@terminal21.de \
--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).