From: Rajesh R <rajesh.arr@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] DPDKthe packet capture performance increases steeply between 11 Rx queues and 12 Rx queues. Any idea why?
Date: Sun, 21 Mar 2021 12:17:51 +0530 [thread overview]
Message-ID: <CAAh6R8Jc9Wp6EfGTR36s4ZT4xeVriGeUE+=BhswaOAtu2ztkpw@mail.gmail.com> (raw)
Hi,
We are experimenting with testpmd packet generation and capture at 100 Gbps
on two machines back to back. We are observing a peculiar behaviour
that the packet capture performance increases steeply between 11 Rx queues
and 12 Rx queues. Any idea why?
The details of the setup are given below:
DPDK version: *19.11*
NIC: *Mellanox ConnectX-5 100 GbE *
OS: *RHEL 8.2(kernel *4.18.0-193)
Application: *Testpmd(txonly on generation side and rxonly on capture side)*
*It is observed that *capture rate increases almost gradually upto* 11 Rx
queues and then increases steeply *to reach line rate *at 12 queues. The
maximum capture rate with 11 Rx queues is around 80 Gbps and with 12 Rx
queues is 99. Gbps.*
*Is it something to do with DPDK ? Or Mellanox specific?*
--
Regards
Rajesh R
reply other threads:[~2021-03-22 12:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAAh6R8Jc9Wp6EfGTR36s4ZT4xeVriGeUE+=BhswaOAtu2ztkpw@mail.gmail.com' \
--to=rajesh.arr@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).