DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/ethdev Bug 1865] net/pcap: support for multiple queues is broken
Date: Thu, 08 Jan 2026 18:22:02 +0000	[thread overview]
Message-ID: <bug-1865-3@http.bugs.dpdk.org/> (raw)

http://bugs.dpdk.org/show_bug.cgi?id=1865

            Bug ID: 1865
           Summary: net/pcap: support for multiple queues is broken
           Product: DPDK
           Version: 25.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: stephen@networkplumber.org
  Target Milestone: ---

When use using pcap PMD the driver advertises support for 16 queues.
But this is not correct. Each queue is a separate instance of pcap handle which
is a then handled as separate file descriptor.

The result is that on transmit each queue overwrites the other in the file. And
can result in truncated or corrupt file. On receive each queue reads all the
packets in the file, there is no RSS or distribution.

Driver should just not report multi-queue or it needs to do locking.

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

                 reply	other threads:[~2026-01-08 18:22 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-1865-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).