DPDK usage discussions
 help / color / mirror / Atom feed
From: Ashish Mishra <ashishm@mvista.com>
To: users <users@dpdk.org>
Subject: [dpdk-users] [ TX-ONLY mode ] No packet count with Testpmd application
Date: Tue, 13 Jul 2021 12:18:29 +0530	[thread overview]
Message-ID: <CAP2Ojcj6qduXz2HU8RUzUxkzb3tBpYtfVQ0UwiBbtzvYAgBoaA@mail.gmail.com> (raw)

Hi Members ,

I am trying to run the testpmd command on a x86_64 machine .
Have shared the log's of
     - Command testpmd
     - Command devbind
     - Steps i followed to get the dpdk source code compiled on host

 ~ : sudo dpdk-testpmd -l 0-3 -n 4 -- -i --nb-cores=2
EAL: Detected 32 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: No available 1048576 kB hugepages reported
EAL: VFIO support initialized
EAL: Probe PCI driver: net_bnxt (14e4:16d8) device: 0000:c6:00.1 (socket 0)
bnxt_hwrm_send_message(): Error(timeout) sending msg 0x0000, seq_id 0
bnxt_hwrm_ver_get(): failed rc:-110
ethdev initialisation failed
EAL: Requested device 0000:c6:00.1 cannot be used
TELEMETRY: No legacy callbacks, legacy socket not created
testpmd: No probed ethernet devices
Interactive-mode selected
testpmd: create a new mbuf pool <mb_pool_0>: n=171456, size=2176, socket=0
testpmd: preferred mempool ops selected: ring_mp_mc
Done
testpmd> set fwd txonly
Set txonly packet forwarding mode
testpmd> start
txonly packet forwarding - ports=0 - cores=0 - streams=0 - NUMA support
enabled, MP allocation mode: native

  txonly packet forwarding packets/burst=32
  packet len=64 - nb packet segments=1
  nb forwarding cores=2 - nb forwarding ports=0
testpmd>
testpmd> stop
Telling cores to stop...
Waiting for lcores to finish...

  +++++++++++++++ Accumulated forward statistics for all
ports+++++++++++++++
  RX-packets: 0              RX-dropped: 0             RX-total: 0
  TX-packets: 0              TX-dropped: 0             TX-total: 0

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Done.


B) I have the the device binding
     #  dpdk-devbind.py -s
         Network devices using DPDK-compatible driver
         ============================================
         0000:c6:00.1 'BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet
Controller 16d8' drv=uio_pci_generic unused=bnxt_en,vfio-pci

C) The dpdk was compiled using below step:
         git clone https://dpdk.org/git/dpdk
         cd dpdk/
         pip3 install meson
         pip3 install pyelftools
         pip3 install ninja
         meson -Dexamples=all build
         ninja -C build
         cd build
         ninja install
         ldconfig
         mkdir -p /dev/hugepages
         mountpoint -q /dev/hugepages || mount -t hugetlbfs nodev
/dev/hugepages
         bash -c 'echo 2048 >
/sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages'

Can a senior member please help me as I am learning things here .
And getting working setup is very important for someone like me who is
starting new here

Thanks ,
Ashish

             reply	other threads:[~2021-07-13  6:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-13  6:48 Ashish Mishra [this message]
2021-07-14 18:03 ` Ashish Mishra
2021-07-15  9:33   ` Ashish Mishra

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=CAP2Ojcj6qduXz2HU8RUzUxkzb3tBpYtfVQ0UwiBbtzvYAgBoaA@mail.gmail.com \
    --to=ashishm@mvista.com \
    --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).