From: Shawn Landden <shawn@git.icu>
To: wireguard@lists.zx2c4.com
Subject: Re: some mips iperf3 tests
Date: Fri, 20 Jul 2018 23:07:49 -0700 [thread overview]
Message-ID: <CA+49okrJFL0AD57AG3snv_UgDqVhY7bh8j=N+sNaFS2peB7btA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 549 bytes --]
https://openwrt.org/toh/hwdata/gl.inet/gl.inet_gl-mt300n_v2
MediaTek MT7628AN 580Mhz single core
with -march=24kc -O2
With 0.0.20180718
receive
[ ID] Interval Transfer Bandwidth Retr
[ 4] 0.00-15.00 sec 64.7 MBytes 36.2 Mbits/sec 246 sender
[ 4] 0.00-15.00 sec 64.6 MBytes 36.1 Mbits/sec
receiver
send
[ ID] Interval Transfer Bandwidth Retr
[ 4] 0.00-15.00 sec 116 MBytes 65.0 Mbits/sec 2 sender
[ 4] 0.00-15.00 sec 115 MBytes 64.2 Mbits/sec
receiver
[-- Attachment #2: Type: text/html, Size: 982 bytes --]
next reply other threads:[~2018-07-21 5:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-21 6:07 Shawn Landden [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-06-28 12:31 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='CA+49okrJFL0AD57AG3snv_UgDqVhY7bh8j=N+sNaFS2peB7btA@mail.gmail.com' \
--to=shawn@git.icu \
--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).