From: Damien Clabaut <damien.clabaut@corp.ovh.com>
To: <dev@dpdk.org>
Subject: [dpdk-dev] Issue with pktgen-dpdk replaying >1500bytes pcap on MCX4
Date: Mon, 25 Sep 2017 13:19:23 -0400 [thread overview]
Message-ID: <5f5aba8a-0dd2-fd64-891b-569d2a4627c8@corp.ovh.com> (raw)
Hello DPDK devs,
I am sending this message here as I did not find a bugtracker on the
website.
If this is the wrong place, I would kindly apologize and ask you to
redirect me to the proper place,
Thank you.
Description of the issue:
I am using pktgen-dpdk to replay a pcap file containing exactly 1 packet.
The packet in question is generated using this Scapy command:
pkt=(Ether(src="ec:0d:9a:37:d1:ab",dst="7c:fe:90:31:0d:52")/Dot1Q(vlan=2)/IP(dst="192.168.0.254")/UDP(sport=1020,dport=1021)/Raw(RandBin(size=8500)))
The pcap is then replayed in pktgen-dpdk:
./app/app/x86_64-native-linuxapp-gcc/pktgen -l 0-7 -- -m [1-7].0 -s
0:pcap/8500Bpp.pcap
When I run this on a machine with Mellanox ConnectX-4 NIC (MCX4), the
switch towards which I generate traffic gets a strange behaviour
#sh int et29/1 | i rate
5 seconds input rate 39.4 Gbps (98.4% with framing overhead), 0
packets/sec
A capture of this traffic (I used a monitor session to redirect all to a
different port, connected to a machine on which I ran tcpdump) gives me
this:
19:04:50.210792 00:00:00:00:00:00 (oui Ethernet) > 00:00:00:00:00:00
(oui Ethernet) Null Unnumbered, ef, Flags [Poll], length 1500
19:04:50.210795 00:00:00:00:00:00 (oui Ethernet) > 00:00:00:00:00:00
(oui Ethernet) Null Unnumbered, ef, Flags [Poll], length 1500
19:04:50.210796 00:00:00:00:00:00 (oui Ethernet) > 00:00:00:00:00:00
(oui Ethernet) Null Unnumbered, ef, Flags [Poll], length 1500
19:04:50.210797 00:00:00:00:00:00 (oui Ethernet) > 00:00:00:00:00:00
(oui Ethernet) Null Unnumbered, ef, Flags [Poll], length 1500
19:04:50.210799 00:00:00:00:00:00 (oui Ethernet) > 00:00:00:00:00:00
(oui Ethernet) Null Unnumbered, ef, Flags [Poll], length 1500
The issue cannot be reproduced if any of the following conditions is met:
- Set the size in the Raw(RandBin()) to a value lower than 1500
- Send the packet from a Mellanox ConnectX-3 (MCX3) NIC (both machines
are indentical in terms of software).
Is this a known problem ?
I remain available for any question you may have.
Regards,
--
Damien Clabaut
R&D vRouter
ovh.qc.ca
next reply other threads:[~2017-09-25 17:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 17:19 Damien Clabaut [this message]
2017-09-26 0:46 ` Yongseok Koh
2017-09-26 12:43 ` Damien Clabaut
2017-09-26 1:46 ` Wiles, Keith
2017-09-26 13:09 ` Damien Clabaut
2017-09-28 20:44 ` Wiles, Keith
2017-10-11 18:59 ` Yongseok Koh
2017-10-12 12:34 ` Damien Clabaut
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=5f5aba8a-0dd2-fd64-891b-569d2a4627c8@corp.ovh.com \
--to=damien.clabaut@corp.ovh.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).