DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH 0/4] pdump: fix capture on ports with hairpin queues
Date: Wed, 28 Oct 2026 07:16:49 -0700	[thread overview]
Message-ID: <20261028141750.310963-1-stephen@networkplumber.org> (raw)

This was reported on dpdk slack channel.

dpdk-dumpcap fails on a port with hairpin queues. The first attempt
reports "Unknown error -22" and every later attempt fails with EEXIST
until the application is restarted.

Several bugs combine: pdump tries to add callbacks to hairpin queues,
the error is returned with the wrong sign, and a partially enabled
capture is not undone. Also the first Rx callback API was missing the
hairpin check the other callback APIs have.

Stephen Hemminger (4):
  ethdev: reject hairpin queue in add first Rx callback
  pdump: fix error code when adding callback fails
  pdump: skip hairpin queues
  pdump: undo partial enable on failure

 lib/ethdev/rte_ethdev.c |   5 ++
 lib/pdump/rte_pdump.c   | 112 +++++++++++++++++++++++++++++++++-------
 2 files changed, 98 insertions(+), 19 deletions(-)

-- 
2.53.0


             reply	other threads:[~2026-10-28 14:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-28 14:16 Stephen Hemminger [this message]
2026-10-28 14:16 ` [PATCH 1/4] ethdev: reject hairpin queue in add first Rx callback Stephen Hemminger
2026-10-28 14:16 ` [PATCH 2/4] pdump: fix error code when adding callback fails Stephen Hemminger
2026-10-28 14:16 ` [PATCH 3/4] pdump: skip hairpin queues Stephen Hemminger
2026-10-28 14:16 ` [PATCH 4/4] pdump: undo partial enable on failure Stephen Hemminger

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=20261028141750.310963-1-stephen@networkplumber.org \
    --to=stephen@networkplumber.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