DPDK usage discussions
 help / color / mirror / Atom feed
From: PATRICK KEROULAS <patrick.keroulas@radio-canada.ca>
To: users@dpdk.org
Subject: [dpdk-users] mlx5 / tcpdump: packet drop
Date: Thu, 23 Jul 2020 17:10:31 -0400	[thread overview]
Message-ID: <CALEF-=CQNwtWouZyrk02sgk5VPzL6-Z79Ven34CPJXhA_Ouddw@mail.gmail.com> (raw)


I'm trying to use tcpdump with dpdk support in order to benefit from
dpdk performance and nice features from tcpdump, like filters etc.
Traffic is constant but quite significant, 6 Gbps, captured by Mellanox

DPDK standalone works like a charm, no packet drop.
$ testpmd -w 0000:01:00.0 -w 0000:01:00.1 -- --enable-rx-timestamp
$ dpdk-pdump -- --pdump 'port=0,queue=*,rx-dev=/tmp/test.pcap'

However,when using libpcap/tcpdump on exact same hardware and
dpdk version, 15% of the pkts are dropped by interface:
$ DPDK_CFG="-dlibrte_mempool_ring.so -dlibrte_common_mlx5.so \
    -dlibrte_pmd_mlx5.so " ./tcpdump -i dpdk:0 -w /tmp/test.pcap
tcpdump: listening on dpdk:0, link-type EN10MB (Ethernet), snapshot
length 262144 bytes
^CUSER1: portid:0, RX-packets: 3778136     RX-errors:  0
RX-bytes:  4767864278  RX-Imissed:  215784
USER1: portid:0, RX-PPS: 613698     RX-Mbps: 6195.72
3778136 packets captured
3778136 packets received by filter
0 packets dropped by kernel
215784 packets dropped by interface

What should I look at first? mempool, queue, dev init sequence?

dpdk v20.05
libpcap 1.8.1

Best regards,


             reply	other threads:[~2020-07-23 21:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-23 21:10 PATRICK KEROULAS [this message]
2020-07-23 23:57 ` Stephen Hemminger
2020-07-24 13:32   ` PATRICK KEROULAS

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CALEF-=CQNwtWouZyrk02sgk5VPzL6-Z79Ven34CPJXhA_Ouddw@mail.gmail.com' \
    --to=patrick.keroulas@radio-canada.ca \
    --cc=users@dpdk.org \


* 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).