From: Stephen Hemminger <stephen@networkplumber.org>
To: Francesco <francesco.montorsi@gmail.com>
Cc: users@dpdk.org
Subject: Re: How to limit testpmd packet generation rate when forward-mode=txonly
Date: Wed, 10 Nov 2021 09:25:31 -0800 [thread overview]
Message-ID: <20211110092531.1caeb7a4@hermes.local> (raw)
In-Reply-To: <CAKW0qijg1wD_Cz35jsj0dAetCEoSra86VNunXCFWxdzGNf5EFg@mail.gmail.com>
On Wed, 10 Nov 2021 17:12:12 +0100
Francesco <francesco.montorsi@gmail.com> wrote:
> Hi all,
> I'm using testpmd as very simple packet generator to test the
> capability of receive packets of my DPDK application. I'm using a
> Mellanox CX5 100Gbps card for the test.
>
> I can successfully launch testpmd with options "--forward-mode=txonly
> --stats-period=3" to push 10.5MPPS on each of the 2 ports of the NIC
> (using just 1 CPU core !!). This is good but I have a couple of
> questions which probably are very basic hopefully:
>
> 1) can I limit the TX rate to e.g. half the value I'm getting now
> (e.g. to 5MPPS) ?
>
> 2) if I want to use more than 1 CPU core for testpmd how can I achieve
> that? I played with --nb-cores=5 and running testpmd in interactive
> mode and then issuing "port config all txq 4" but still no luck...
> testpmd will keep using only 1 CPU core
>
> 3) when I run testpmd in batch mode I get a nice report about
> "throughput (since last show)" every stats period. How can I tell
> testpmd to show me PPS/bytes-per-second reporting also when I start
> the application with "-i" (interactive mode)?
>
> Thanks a lot for any hint,
>
> Francesco Montorsi
Use a real packet generator like trex if you need more control.
prev parent reply other threads:[~2021-11-10 17:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 16:12 Francesco
2021-11-10 17:25 ` Stephen Hemminger [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=20211110092531.1caeb7a4@hermes.local \
--to=stephen@networkplumber.org \
--cc=francesco.montorsi@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).