From: Roman Mamedov <rm@romanrm.net>
To: Germano Massullo <germano.massullo@gmail.com>
Cc: Antonio Quartulli <a@unstable.cc>,
WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Mini PCIE HW accelerator for ChaCha20
Date: Mon, 17 Jun 2024 17:41:59 +0500 [thread overview]
Message-ID: <20240617174159.46b69d3b@nvm> (raw)
In-Reply-To: <4940a8fd-6e87-49a4-83e0-8daa69e7a68f@gmail.com>
On Mon, 17 Jun 2024 14:32:19 +0200
Germano Massullo <germano.massullo@gmail.com> wrote:
> Got it. That configuration will not improve the throughput cause the
> reason why I started this benchmark is finding out the bottleneck in my
> configuration, which is very similar to the one you described
Point is that iperf itself is using a huge amount of CPU. You can run your
test and launch "top" in another SSH window. In my experience for slow CPUs
during such tests the CPU use may be like 60% iperf.
If your typical scenario is router just forwarding packets between networks
and into WG tunnel, and not providing any network services itself (such as
Samba), testing with iperf launched on the router will not be representative
of real-world usage bottleneck or lack thereof.
--
With respect,
Roman
next prev parent reply other threads:[~2024-06-17 12:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 14:11 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 [this message]
2024-06-17 14:31 ` Germano Massullo
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=20240617174159.46b69d3b@nvm \
--to=rm@romanrm.net \
--cc=a@unstable.cc \
--cc=germano.massullo@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).