From: Padam Jeet Singh <padam.singh@inventum.net>
To: users@dpdk.org
Subject: [dpdk-users] Fragmentation and Reassembly issues
Date: Sat, 18 Mar 2017 08:33:11 +0530 [thread overview]
Message-ID: <94242C63-25F0-4AB4-A8F9-F981083F3A38@inventum.net> (raw)
Hi,
I am using the IPv4 reassembly function (rte_ipv4_frag_reassemble_packet) on RX, and IPv4 fragmentation function (rte_ipv4_fragment_packet) on TX.
When I am putting this code into our production network, after a few hours the Ethernet port’s TX stops working. All packets sent to the PMD using rte_eth_tx_burst fail (returned 0 = no packets sent).
If I disable the reassembly and drop all incoming fragments, but continue to do fragmentation on TX (since the MTU is different on RX and TX ports) then everything works normally.
Any pointers on what could be wrong when forwarding packets using this scheme?
Thanks,
Padam
reply other threads:[~2017-03-18 3: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=94242C63-25F0-4AB4-A8F9-F981083F3A38@inventum.net \
--to=padam.singh@inventum.net \
--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).