DPDK usage discussions
 help / color / mirror / Atom feed
From: Filip Janiszewski <contact@filipjaniszewski.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] testpmd and jumbo frames
Date: Tue, 26 Feb 2019 07:49:32 +0100	[thread overview]
Message-ID: <6a0871c4-c884-b61a-e1fc-4752531a4a2f@filipjaniszewski.com> (raw)

Hi,

Can someone suggest the proper configuration required to test jumbo
frames along with scatter mode using testpmd?

I'm running the tool as follow:

.
sudo ./testpmd -l 0-3 -n 4 -- -i --max-pkt-len=9600 --enable-scatter
--txd=512 --rxd=512 --forward-mode=flowgen
.

then attempting to set the packet length:

.
testpmd> set txpkts 9036
length[0]=9036 > mbuf_data_size=2176 - give up
.

According to the documentation
(https://doc.dpdk.org/guides/testpmd_app_ug/run_app.html), the option
txpkts should configure:

.
Set TX segment sizes or total packet length. Valid for tx-only and
flowgen forwarding modes.
.

So I was expecting to be able to set the packet length in this way, but
somehow it doesn't work and when I hit start the packets have always a
length of 60 bytes:

.
 src=00:01:02:03:04:00 - dst=00:01:02:03:04:01 - type=0x0800 - length=60
- nb_segs=1 - hw ptype: L2_ETHER L3_IPV4_EXT_UNKNOWN L4_UDP  - sw ptype:
L2_ETHER L3_IPV4 L4_UDP  - l2_len=14 - l3_len=20 - l4_len=8 - Send queue=0x0
.

I've attempted to set the queue capabilities (scatter and JF) by hand with:

.
testpmd> port config 1 rx_offload scatter on
testpmd> port config 1 rx_offload jumbo_frame on
.

(repeated for both port) but this doesn't helped, so, how do I test a
card using testpmd with packets bigger than 2176?

Thanks

-- 
BR, Filip
+48 666 369 823

             reply	other threads:[~2019-02-26  6:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-26  6:49 Filip Janiszewski [this message]
2019-02-26 13:09 ` Rami Rosen
2019-02-26 13:52   ` Filip Janiszewski

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=6a0871c4-c884-b61a-e1fc-4752531a4a2f@filipjaniszewski.com \
    --to=contact@filipjaniszewski.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).