From: Suchetha p <suchetha2005@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] IPV4 and VLAN RX packets from NIC donot have the mbuf offload flag set resulting in packet drop - DPDK
Date: Wed, 26 Jun 2019 19:15:01 +0530 [thread overview]
Message-ID: <CAOGjjAP1QNsj-3hMN=xWMSu6tE6+i+2E31CfPxY+z7C2-xrWgA@mail.gmail.com> (raw)
After upgrading the DPDK and RHEL OS to latest version I observe that
offload flags were not set in the packets received from NIC for eth type
VLAN and IPV4.Can this be a Driver issue ?How to fix this? It was required
to explicitly set the offload flags in the ingress VLAN and IPV4 packets.
if (ETHER_TYPE_VLAN == eth_type) { m->ol_flags |= PKT_RX_VLAN_PKT;
}
if (ETHER_TYPE_IPv4 == eth_type) {
m->ol_flags |= PKT_RX_IPV4_HDR;
}
If these offload flags were not set in the mbuf the packet would get
dropped and will not be forwarded to the Tap device. But the offload flag
setting per NIC received packet in the application is causing some
performance issue and delay in data transfer. TCP segment
loss,retransmissions and TX Tap drops were observed. These changes with
respect to offload flag setting for RX VLAN and IPV4 packets were not
required with old DPDK and RHEL6 and packets were getting forwarded from
NIC to Tap device and vice versa without any issue. So is anything changed
with respect to DPDK and RHEL 7 for ingress packets ?Any configuration
changes required with new DPDK to instruct the Hardware to set the offload
flags ? Is it required to set CKSUM/ offload flags for TCP packets with new
DPDK 18.08 to avoid TCP segment loss /DUP ACK and retransmissions? Please
suggest.
reply other threads:[~2019-06-26 13: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='CAOGjjAP1QNsj-3hMN=xWMSu6tE6+i+2E31CfPxY+z7C2-xrWgA@mail.gmail.com' \
--to=suchetha2005@gmail.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).