WireGuard Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Germano Massullo <germano.massullo@gmail.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>,
	Roman Mamedov <rm@romanrm.net>
Cc: Antonio Quartulli <a@unstable.cc>
Subject: Re: Mini PCIE HW accelerator for ChaCha20
Date: Mon, 17 Jun 2024 16:31:49 +0200	[thread overview]
Message-ID: <9e717774-c1cd-493f-abfd-fcf3d75eec8d@gmail.com> (raw)
In-Reply-To: <20240617174159.46b69d3b@nvm>

After having checked that iperf3 was indeed consuming a lot of a CPU 
core on the Turris Omnia, I modified the Wireguard topology in order to 
have the router to just be the Wireguard gateway among two LAN computers 
( [A] <--wireguard--> [C] <--wireguard--> [B] ), and I have run the 
iperf3 among such computers
iperf3 -c x.x.x.x -P 4 -Z bbr
and the throughput was ~320 Mbit/s. Considering that the router had to 
handle two Wireguard tunnels, one could guess (without any claim of 
accuracy due lack of more accurate tests), that the maximum Wireguard 
throughput that such router can handle is ~2x 320 Mbit/s = ~640 Mbit/s

[A]: Ryzen 5 3600 - kernel 5.14.0-427.18.1.el9_4.x86_64
[B]: Ryzen 7 PRO 6850U -  kernel 6.8.11-300.fc40.x86_64
[C]: Turris Omnia - TurrisOS 7.0.0, kernel 5.15.148

      reply	other threads:[~2024-06-17 14:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-12 14:11 Mini PCIE HW accelerator for ChaCha20 Germano Massullo
2024-06-16 13:47 ` Max Schulze
2024-06-16 14:59   ` Germano Massullo
2024-06-16 19:00     ` Max Schulze
2024-06-17  9:21       ` Germano Massullo
2024-06-17  9:45         ` Antonio Quartulli
2024-06-17 11:08           ` Germano Massullo
2024-06-17 11:42             ` Antonio Quartulli
2024-06-17 12:32               ` Germano Massullo
2024-06-17 12:41                 ` Roman Mamedov
2024-06-17 14:31                   ` Germano Massullo [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=9e717774-c1cd-493f-abfd-fcf3d75eec8d@gmail.com \
    --to=germano.massullo@gmail.com \
    --cc=a@unstable.cc \
    --cc=rm@romanrm.net \
    --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