From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 295] max_rx_pkt_len issues with i40e dpdk SRIOV driver net_i40e_vf.
Date: Thu, 12 Sep 2019 05:07:00 +0000 [thread overview]
Message-ID: <bug-295-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=295
Bug ID: 295
Summary: max_rx_pkt_len issues with i40e dpdk SRIOV driver
net_i40e_vf.
Product: DPDK
Version: 18.02
Hardware: x86
OS: All
Status: RESOLVED
Severity: normal
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: lavaraj@gmail.com
CC: xiao.zhang@intel.com
Target Milestone: ---
Resolution: DUPLICATE
CC: xiao.zhang@intel.com
Status: RESOLVED
max_rx_pkt_len issues with i40e dpdk SRIOV driver (net_i40e_vf).
================================================================
When deployed an SRIOV setup with Intel® Ethernet 700 Series 40GB NIC, we
noticed the traffic with default mtu (1500) is not working.
The maximum MSS which was worked is 1456 ( instead of the default value 1460).
On debugging, it is found that the driver is actually setting the
dev_data->dev_conf.rxmode.max_rx_pkt_len to 1518(ETHER_MAX_LEN) which is wrong.
The max len is not including the vlan tag len( also not including QinQ).
The ETH Overhead is defined as below
#define I40E_ETH_OVERHEAD \
(ETHER_HDR_LEN + ETHER_CRC_LEN + I40E_VLAN_TAG_SIZE * 2)
which is equal to 26
So for supporting an MTU size of 1500, the max_rx_pkt_len should be 1526
instead of 1518.
The i40evf_dev_mtu_set API also wrongly checking the framesize against
ETHER_MAX_LEN(1518) to set the jumbo_frame mode.
The attached patch resolved the issue for our testing.
Please verify and fix the issue.
Thanks and Regards,
Lava
--- Comment #1 from Xiao Zhang (xiao.zhang@intel.com) ---
duplicate of 296
*** This bug has been marked as a duplicate of bug 296 ***
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2019-09-12 5:07 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=bug-295-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.