DPDK usage discussions
 help / color / mirror / Atom feed
From: Luca Anastasio <anastasio.lu@gmail.com>
To: users@dpdk.org
Subject: Test setup information
Date: Wed, 28 Dec 2022 16:05:25 +0100	[thread overview]
Message-ID: <9f03bfd8-fafe-38da-31b3-74a79ab1dae3@gmail.com> (raw)

Dear DPDK developers,
I would like to ask for some clarifications, especially regarding the 
test setups used in whitepapers and performance reports (such as 
https://fast.dpdk.org/doc/perf/DPDK_21_11_Mellanox_NIC_performance_report.pdf).
I couldn't find an explicit statement on whether the packet generator 
has to be started after or before starting the test program.

In case of starting the packet generator before the test program, are 
there any precautions to be observed?
Are there any performance issues due to receiving too many packets 
between the port initialization and the start of RX burst invocation?
Is there any specific sequence of function calls to stick to in this case?

Looking forward to your kind reply
Best regards
Luca Anastasio


                 reply	other threads:[~2023-01-03  9:34 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=9f03bfd8-fafe-38da-31b3-74a79ab1dae3@gmail.com \
    --to=anastasio.lu@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).