All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 802] Need help with ipv4_multicast app in DPDK 20.08
Date: Tue, 31 Aug 2021 07:21:54 +0000	[thread overview]
Message-ID: <bug-802-3@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 802
           Summary: Need help with ipv4_multicast app in DPDK 20.08
           Product: DPDK
           Version: 20.08
          Hardware: x86
                OS: All
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: examples
          Assignee: dev@dpdk.org
          Reporter: rashmi.keshavarao@hpe.com
  Target Milestone: ---

Hi,
We are trying to use the ipv4_multicast app in DPDK examples. 
However, we are not able to get it to run as expected.

The behavior that we are seeing is that packets are being sent from a packet
generator but they are not being received by the APP. We have tried debugging
the app by putting prints at various places but still don't have a clue on what
is wrong.

We tried other examples apps like testpmd, l2fwd etc and these are working
flawlessly.

Need inputs from the DPDK experts on the ipv4_multicast app.

Command used:

./<build_dir>/examples/ipv4_multicast -c 0x1 -n 1 -- -p 0x5 -q 2

DPDK Version: 20.08
NIC: XXV710 (fw version: 8.3)
Bound to: vfio-pci UIO


With the above command:
rte_eth_rx_burst() returns 0 in the ipv4_multicast app even when packets are
being sent to the NIC/port.

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

             reply	other threads:[~2021-08-31  7:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-31  7:21 bugzilla [this message]
2023-06-12 20:55 ` [Bug 802] Need help with ipv4_multicast app in DPDK 20.08 bugzilla

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-802-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.