From: Antonio Di Bacco <a.dibacco.ks@gmail.com>
To: users@dpdk.org
Subject: tap device speed
Date: Mon, 2 Oct 2023 21:13:03 +0200 [thread overview]
Message-ID: <CAO8pfFmA4-brn3zKBqxmVfauxHm+uvhFBAkxn667dgoBQX3hSg@mail.gmail.com> (raw)
I'm doing a test where we have a couple of tap devices, the two
devices are seen by testpmd that is setup in forward mode.
On the linux side, the two tap devices are confined in different
network namespaces and in one namespace we have an iperf server while
on the other namespace the iperf client sending either UDP or TCP.
I expected a bandwidth in the range of few gpbs while the actual
measured bandwidth is a few gigabits.
I suppose I need to configure the tap devices with optimized
parameters but I don't know where to look for advice.
If I try to use the loopback interface I can get something 40 gbps
with a command like this:
iperf -c 127.0.0.1 -u -i 1 -b 40g -t 10 -l 40000
.
next reply other threads:[~2023-10-02 19:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 19:13 Antonio Di Bacco [this message]
2023-10-02 21:21 ` Stephen Hemminger
2023-10-03 8:49 ` Antonio Di Bacco
2023-10-03 16:01 ` Stephen Hemminger
2023-10-04 6:17 ` David Marchand
2023-10-04 7:08 ` Maxime Coquelin
2023-10-04 7:42 ` Antonio Di Bacco
2023-10-04 7:49 ` Maxime Coquelin
2023-10-09 17:48 ` Antonio Di Bacco
2023-10-09 18:42 ` Maxime Coquelin
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=CAO8pfFmA4-brn3zKBqxmVfauxHm+uvhFBAkxn667dgoBQX3hSg@mail.gmail.com \
--to=a.dibacco.ks@gmail.com \
--cc=users@dpdk.org \
/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).