DPDK usage discussions
 help / color / mirror / Atom feed
From: Navin Srinivas <g.navinsrinivas@gmail.com>
To: dev@dpdk.org, users <users@dpdk.org>
Subject: Issue on capturing using DPDK Pdump on secondary interface.
Date: Thu, 25 Aug 2022 11:43:11 +0530	[thread overview]
Message-ID: <CACOt6jyUqnus_ZYABKfmyT-Qg+7naqF_S7fe-ph7GztGOpJM4g@mail.gmail.com> (raw)
In-Reply-To: <CACOt6jzqtA3rwBMww3NqfYwXCfE9J8g=ym983P8ZEF77ciRtmw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1005 bytes --]

Hello,

We are facing a strange issue, we have the following setup for our
application. We wanted to capture packets using dpdk pdump for our
application, and started to notice an issue in capturing on DPDK 21.11
So we went back to DPDK 20.11 and we still saw the issue.

[image: image.png]
Think there is an issue in the pdump library to capture packets on the
secondary interface. But I'm not sure where to look.
APP1 - Primary APP
APP2 - Secondary APP.
Ports and ring inits are done by APP1 for APP2.

We are able to capture packets using the standard example application of
pdump and capture on port 0, but we are not able to capture on port1.

Has anyone come across this issue? Is there an open bug for this?
The multi process is working properly, and we are able to transmit and
receive packets on the secondary interface without any issue. We are facing
issue only on capturing packets on that interface(port1).

Are there any pointers where I can start to look?

Thanks & Regards,
Navin Srinivas

[-- Attachment #1.2: Type: text/html, Size: 1386 bytes --]

[-- Attachment #2: image.png --]
[-- Type: image/png, Size: 6463 bytes --]

       reply	other threads:[~2022-08-25  6:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CACOt6jzqtA3rwBMww3NqfYwXCfE9J8g=ym983P8ZEF77ciRtmw@mail.gmail.com>
2022-08-25  6:13 ` Navin Srinivas [this message]
2022-09-16 16:42   ` Stephen Hemminger
     [not found] <mailman.1.1663408802.31806.users@dpdk.org>
2022-09-23  6:36 ` Varghese, Vipin

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=CACOt6jyUqnus_ZYABKfmyT-Qg+7naqF_S7fe-ph7GztGOpJM4g@mail.gmail.com \
    --to=g.navinsrinivas@gmail.com \
    --cc=dev@dpdk.org \
    --cc=users@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).