From: "Knight, Joshua" <Joshua.Knight@netscout.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: dpdk-pktgen: jumbo frames on AWS EC2
Date: Tue, 2 Nov 2021 16:45:32 +0000 [thread overview]
Message-ID: <DM6PR01MB4283421A185CC4EDB068A90D878B9@DM6PR01MB4283.prod.exchangelabs.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2358 bytes --]
I’m attempting to run pktgen on an AWS EC2 instance with jumbo frames. When I use the -j option to enable jumbo frames, it attempts to setup a max_rx_pkt_len size of 9618 which causes it to crash. It’s reporting the max valid value is 9216.
Is there a way to override it to set 9216 instead at runtime? Or would I need to modify and recompile pktgen/dpdk?
Looking at another interface using the kernel driver, the max mtu reported is 9216 so I’m also not sure where the 9618 comes from or why it’s being used instead of 9216. Perhaps I’m misunderstanding what should work out-of-the-box and what needs to be tweaked during compilation time.
I’m using pktgen 21.05.0 and dpdk 21.08.
Copyright(c) <2010-2021>, Intel Corporation. All rights reserved. Powered by DPDK
EAL: Detected 72 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Detected shared linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: No available 1048576 kB hugepages reported
EAL: VFIO support initialized
EAL: Device 0000:00:05.0 is not NUMA-aware, defaulting socket to 0
EAL: Device 0000:00:06.0 is not NUMA-aware, defaulting socket to 0
EAL: Probe PCI driver: net_ena (1d0f:ec20) device: 0000:00:06.0 (socket 0)
EAL: Device 0000:00:07.0 is not NUMA-aware, defaulting socket to 0
TELEMETRY: No legacy callbacks, legacy socket not created
**** Jumbo Frames of 9618 enabled.
*** Copyright(c) <2010-2021>, Intel Corporation. All rights reserved.
*** Pktgen created by: Keith Wiles -- >>> Powered by DPDK <<<
Port: Name IfIndex Alias NUMA PCI
0: net_ena 0 0 1d0f:ec20/00:06.0
Initialize Port 0 -- TxQ 6, RxQ 1
Ethdev port_id=0 max_rx_pkt_len 9618 > max valid value 9216
!PANIC!: Cannot configure device: port=0, Num queues 1,6 (22)Invalid argument
PANIC in pktgen_config_ports():
Cannot configure device: port=0, Num queues 1,6 (22)Invalid argument
6: [pktgen(+0xa8de) [0x55d0401ef8de]]
5: [/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x7ffb0b4ab0b3]]
4: [pktgen(+0xa454) [0x55d0401ef454]]
3: [pktgen(+0x31a2e) [0x55d040216a2e]]
2: [/usr/local/lib/x86_64-linux-gnu/librte_eal.so.21(__rte_panic+0xcd) [0x7ffb0b869e9f]]
1: [/usr/local/lib/x86_64-linux-gnu/librte_eal.so.21(rte_dump_stack+0x32) [0x7ffb0b88f602]]
Aborted
Thanks,
Josh
[-- Attachment #2: Type: text/html, Size: 9334 bytes --]
reply other threads:[~2021-11-02 16:45 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=DM6PR01MB4283421A185CC4EDB068A90D878B9@DM6PR01MB4283.prod.exchangelabs.com \
--to=joshua.knight@netscout.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).