From: "Balázs Lugossy" <balazs.lugossy@ericsson.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] max_rx_pkt_len
Date: Sat, 19 Jun 2021 15:18:49 +0000 [thread overview]
Message-ID: <PR3PR07MB822503820113F4F555E67E75E80C9@PR3PR07MB8225.eurprd07.prod.outlook.com> (raw)
Hi DPDK developers,
We have an external DPDK KNI interface in our product, and we experienced that ethernet payload of size 1500 cannot be received, only 1496. It is important that the traffic is VLAN tagged. We have encountered this report: https://dev.dpdk.narkive.com/xGGOQC8R/dpdk-dev-issue-with-mtu-max-rx-pkt-len-handling-by-different-nics-pmd-drivers, which pretty much similar to our case. We started to experiment with max_rx_pkt_len, but no matter what we set it to it won't work with 1500 payload only 1496. Then we checked rte_eth_dev_configure and realized that max_rx_pkt_len is defaulted to ETHER_MAX_LEN in case max_rx_pkt_len is set to > ETHER_MAX_LEN. ETHER_MAX_LEN is 1518 and thus doesn't contain enough bytes for possible vlan header. As a workaround we have enabled JUMBO frames and set max_rx_pkt_len to 2048. This way traffic is fine. But I want to know what should be the official way to support 1500 payload in VLAN tagged frames with standard frame size?
Regards,
Balazs
reply other threads:[~2021-06-21 7:03 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=PR3PR07MB822503820113F4F555E67E75E80C9@PR3PR07MB8225.eurprd07.prod.outlook.com \
--to=balazs.lugossy@ericsson.com \
--cc=dev@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).