DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1526] rte_eth_rx_burst is blocking in libpcap pmd on no packets
Date: Thu, 22 Aug 2024 14:00:56 +0000	[thread overview]
Message-ID: <bug-1526-3@http.bugs.dpdk.org/> (raw)

[-- Attachment #1: Type: text/plain, Size: 1477 bytes --]

https://bugs.dpdk.org/show_bug.cgi?id=1526

            Bug ID: 1526
           Summary: rte_eth_rx_burst is blocking in libpcap pmd on no
                    packets
           Product: DPDK
           Version: 24.03
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: ofer.d@claroty.com
  Target Milestone: ---

Hi,

I see a weird behaviour when using libpcap pmd, that when no packets getting to
interface, the call to rte_eth_rx_burst is blocking.

I see the following stack:
#0  0x00007f17d496cbcf in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x000055f290d6ef84 in pcap_wait_for_frames_mmap ()
#2  0x000055f290d71db0 in pcap_read_linux_mmap_v3 ()
#3  0x000055f290d50c8f in pcap_next ()
#4  0x000055f290714263 in eth_pcap_rx ()
#5  0x000055f29018f2f2 in rte_eth_rx_burst (nb_pkts=64, rx_pkts=0x7ffec08382b0,
queue_id=<optimized out>, port_id=<optimized out>) at
/usr/local/stow/dpdk/include/rte_ethdev.h:6110

I looked in libpcap and it indeed seems that pcap_read_linux_mmap_v3 is
blocking, and what is meant to be called, when using dpdk, is
pcap_dpdk_dispatch (which indeed seems non blocking).

Can you please help debug and understand why is it behaving like that?

Thanks ahead!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #2: Type: text/html, Size: 3353 bytes --]

                 reply	other threads:[~2024-08-22 14:00 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-1526-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).