From: Lijuan Tu <lijuan.tu@intel.com>
To: dts@dpdk.org
Cc: Lijuan Tu <lijuan.tu@intel.com>
Subject: [dts] [PATCH] test_plan/jumboframes: fix command line
Date: Thu, 7 May 2020 17:43:14 +0800 [thread overview]
Message-ID: <1588844594-17383-1-git-send-email-lijuan.tu@intel.com> (raw)
* fix command line
* refine description
Signed-off-by: Lijuan Tu <lijuan.tu@intel.com>
---
test_plans/jumboframes_test_plan.rst | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/test_plans/jumboframes_test_plan.rst b/test_plans/jumboframes_test_plan.rst
index 71af780..a713ee5 100644
--- a/test_plans/jumboframes_test_plan.rst
+++ b/test_plans/jumboframes_test_plan.rst
@@ -39,6 +39,11 @@ to receive Jumbo Frames with a configurable maximum packet length that is
greater than the standard maximum Ethernet frame length (1518 bytes), up to
a maximum value imposed by the hardware.
+.. note::
+
+ Maximum Packet Length = MTU(Maximum Transmission Unit) + 14(src mac + dst mac) + 4(CRC)
+ e.g., 1518 = 1500 + 14 + 4
+
Prerequisites
=============
@@ -54,13 +59,12 @@ Assuming that ports ``0`` and ``1`` of the test target are directly connected
to the traffic generator, launch the ``testpmd`` application with the following
arguments::
- ./build/app/testpmd -c ffffff -n 3 -- -i --rxd=1024 --txd=1024 \
- --burst=144 --txpt=32 --txht=0 --txfreet=0 --rxfreet=64 \
- --mbcache=200 --portmask=0x3 --mbuf-size=2048 --max-pkt-len=9600
+ ./build/app/testpmd -c ffffff -n 6 -- -i --portmask=0x3 --max-pkt-len=9600 \
+ --tx-offloads=0x00008000
The -n command is used to select the number of memory channels. It should match the number of memory channels on that setup.
-Setting the size of the mbuf data buffer to 2048 and the maximum packet length
+Setting tx-offload to 0x8000 and the maximum packet length
to 9600 (CRC included) makes input Jumbo Frames to be stored in multiple
buffers by the hardware RX engine.
--
1.8.3.1
next reply other threads:[~2020-05-07 1:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 9:43 Lijuan Tu [this message]
2020-05-12 7:32 ` Tu, Lijuan
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=1588844594-17383-1-git-send-email-lijuan.tu@intel.com \
--to=lijuan.tu@intel.com \
--cc=dts@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).