From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 568] mlx5 flow match & drop performance problem
Date: Mon, 02 Nov 2020 01:05:01 +0000 [thread overview]
Message-ID: <bug-568-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=568
Bug ID: 568
Summary: mlx5 flow match & drop performance problem
Product: DPDK
Version: 19.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: vhost/virtio
Assignee: dev@dpdk.org
Reporter: kangzy1982@qq.com
Target Milestone: ---
Kernel ver: 5.4.x
FW ver: 5.1-2.3.7
CPU : Intel(R) Xeon(R) Platinum 9242 CPU @ 2.30GHz
NIC: Mellanox Technologies MT27800 Family [ConnectX-5]
dpdk ver: 19.11 & 20.5 & 20.8
testpmd :
testpmd --log-level=8 -c 0xfffffffffffe --socket-mem=5120,5120 -n 4 -r 2 -w
81:00.0 -- -i --rxq=16 --txq=16 --nb-cores=16 --forward-mode icmpecho
without flows:
1> ixia generate 20Gbps 64bytes TCP traffic & 5 icmp echo request;
2> testpmd icmpecho will drop all & reply all icmp request
with these flows:
flow create 0 ingress pattern eth / ipv4 / tcp / end actions count / drop / end
flow create 0 ingress pattern eth / ipv4 / icmp / end actions queue index 3 /
mark id 3 / end
1> ixia generate 50Gbps 64bytes TCP traffic & 5 icmp echo request;
2> testpmd icmpecho will only receive all icmp request packets & reply;
without drop tcp flows, tespmd is ok!
but with drop tcp flows, testpmd actually can't receive all icmp request
packets!
it seem that NIC firmware cause icmp packets lost!
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-11-02 1:05 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-568-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 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).