DPDK usage discussions
 help / color / mirror / Atom feed
From: Nishant Verma <vnish11@gmail.com>
To: Erfan Mozaffariahrar <erfan.mozaffariahrar@uni-tuebingen.de>
Cc: USERS <users@dpdk.org>
Subject: Re: [dpdk-users] PCI device 0000:01:00.0 on NUMA socket -1 && !PANIC!: *** Did not find any ports to use ***
Date: Mon, 6 Jul 2020 10:03:34 -0400	[thread overview]
Message-ID: <CAHhCjUFaSz-N4T8gxRxDZxo4RoDcUiyLA+M7Sz8gG1gLiyx2Hw@mail.gmail.com> (raw)
In-Reply-To: <20200706155143.Horde.EcshLnAo_6WgYNHJ8nopqIP@webmail.uni-tuebingen.de>

Ok. In that. case your hello world program is good. The output that you are
seeing is correct.
Coming to pktgen, share your default.cfg and output of `lspci | grep Ether"

On Mon, Jul 6, 2020 at 9:51 AM Erfan Mozaffariahrar <
erfan.mozaffariahrar@uni-tuebingen.de> wrote:

> Dear Nishant,
>
>
> Quoting Nishant Verma <vnish11@gmail.com>:
>
> > Hi Erfan,
> >
> > It would be great if you let us know how you are planning to execute
> > helloworld and pktgen.
> > Because HelloWorld is a demo app just to show core functionality nothing
> > else, while pktgen can be used for all sorts of packet related
> operations.
> >
>
> I used this documentation
> https://doc.dpdk.org/guides/linux_gsg/index.html for Linux.
> I also tried to run pktgen using the following guide:
> https://pktgen-dpdk.readthedocs.io/en/latest/
> I just wanted to get familiar with the DPDK.
> My goal is to have a DPDK platform to evaluate different algorithms
> and also for vSwitches.
>
> > One more thing, if you have allocated ports to one DPDK application then
> > you can't allocate those ports to any application. For example, if one
> > application is using one PCI then for another application that will be
> > blacklisted.
>
> I didn't run them simultaneously. I first ran the helloworld and tried
> pktgen but failed in both of them.
>
>
> Thanks,
> Erfan
> >
> > Thanks.
> >
> > On Mon, Jul 6, 2020 at 6:18 AM Erfan Mozaffariahrar <
> > erfan.mozaffariahrar@uni-tuebingen.de> wrote:
> >
> >> Hey guys,
> >>
> >> I'm new at DPDK and want to run helloworld and pktgen applications.
> >> I have a quad port Intel I350 NIC.
> >> I binded VFIO-PCI drivers using dpdk-devbind.py
> >>
> >>
> >> ./usertools/dpdk-devbind.py --status
> >>
> >> Network devices using DPDK-compatible driver
> >> ============================================
> >> 0000:01:00.0 'I350 Gigabit Network Connection 1521' drv=vfio-pci
> >> unused=igb,uio_pci_generic
> >> 0000:01:00.1 'I350 Gigabit Network Connection 1521' drv=vfio-pci
> >> unused=igb,uio_pci_generic
> >> 0000:01:00.2 'I350 Gigabit Network Connection 1521' drv=vfio-pci
> >> unused=igb,uio_pci_generic
> >> 0000:01:00.3 'I350 Gigabit Network Connection 1521' drv=vfio-pci
> >> unused=igb,uio_pci_generic
> >>
> >>
> >> When I run the helloworld application:
> >>
> >> sudo ./build/helloworld -l 0-3 -n 1
> >> EAL: Detected 4 lcore(s)
> >> EAL: Detected 1 NUMA nodes
> >> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
> >> EAL: Selected IOVA mode 'PA'
> >> EAL: Probing VFIO support...
> >> EAL: VFIO support initialized
> >> EAL: PCI device 0000:00:19.0 on NUMA socket -1
> >> EAL:   Invalid NUMA socket, default to 0
> >> EAL:   probe driver: 8086:1502 net_e1000_em
> >> EAL: PCI device 0000:01:00.0 on NUMA socket -1
> >> EAL:   Invalid NUMA socket, default to 0
> >> EAL:   probe driver: 8086:1521 net_e1000_igb
> >> EAL:   using IOMMU type 8 (No-IOMMU)
> >> EAL: PCI device 0000:01:00.1 on NUMA socket -1
> >> EAL:   Invalid NUMA socket, default to 0
> >> EAL:   probe driver: 8086:1521 net_e1000_igb
> >> EAL: PCI device 0000:01:00.2 on NUMA socket -1
> >> EAL:   Invalid NUMA socket, default to 0
> >> EAL:   probe driver: 8086:1521 net_e1000_igb
> >> EAL: PCI device 0000:01:00.3 on NUMA socket -1
> >> EAL:   Invalid NUMA socket, default to 0
> >> EAL:   probe driver: 8086:1521 net_e1000_igb
> >> hello from core 1
> >> hello from core 2
> >> hello from core 3
> >> hello from core 0
> >>
> >> ****
> >>
> >> Running pktgen:
> >>
> >> >>> sdk '/home/mozaffari/dpdk-20.02', target 'x86_64-native-linux-gcc'
> >> Setup DPDK to run 'pktgen' application from cfg/default.cfg file
> >> mozaffari@mozaffari-2:~/pktgen-dpdk$ ./tools/run.py default
> >> >>> sdk '/home/mozaffari/dpdk-20.02', target 'x86_64-native-linux-gcc'
> >>     Trying ./app/x86_64-native-linux-gcc/pktgen
> >> sudo -E
> >>
> LD_LIBRARY_PATH=/home/mozaffari/dpdk-20.02/x86_64-native-linux-gcc/lib/x86_64-linux-gnu
> >> ./app/x86_64-native-linux-gcc/pktgen -l 0-3 -n 4 --proc-type auto
> >> --log-level 7 --file-prefix pg -w 05:00.0,safe-mode-support=1 -w
> >> 84:00.0,safe-mode-support=1 -w 03:00.0 -w 81:00.0 -- -v -T -P -j -m
> [3:4].0
> >> -m [5:6].1 -m [16:17].2 -m [18:19].3 -f
> >> themes/black-yellow.theme
> >>
> >> Copyright (c) <2010-2019>, Intel Corporation. All rights reserved.
> >> Powered by DPDK
> >> EAL: Detected 4 lcore(s)
> >> EAL: Detected 1 NUMA nodes
> >> EAL: Auto-detected process type: PRIMARY
> >> EAL: Multi-process socket /var/run/dpdk/pg/mp_socket
> >> EAL: Selected IOVA mode 'VA'
> >> EAL: Probing VFIO support...
> >> EAL: VFIO support initialized
> >> Lua 5.3.3  Copyright (C) 1994-2016 Lua.org, PUC-Rio
> >> **** Jumbo Frames of 9618 enabled.
> >>
> >> *** Copyright (c) <2010-2019>, Intel Corporation. All rights reserved.
> >> *** Pktgen created by: Keith Wiles -- >>> Powered by DPDK <<<
> >>
> >> >>> Packet Burst 64, RX Desc 1024, TX Desc 2048, mbufs/port 16384,
> >> >>> mbuf cache 2048
> >>   Port: Name         IfIndex Alias        NUMA  PCI
> >>
> >> !PANIC!: *** Did not find any ports to use ***
> >> PANIC in pktgen_config_ports():
> >> *** Did not find any ports to use ***
> >> 6: [./app/x86_64-native-linux-gcc/pktgen(_start+0x2a) [0x560ab1edd76a]]
> >> 5: [/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)
> >> [0x7f9e0d7beb97]]
> >> 4: [./app/x86_64-native-linux-gcc/pktgen(main+0x9d4) [0x560ab1d054a4]]
> >> 3: [./app/x86_64-native-linux-gcc/pktgen(pktgen_config_ports+0x2471)
> >> [0x560ab1f12f51]]
> >> 2: [./app/x86_64-native-linux-gcc/pktgen(__rte_panic+0xc5)
> >> [0x560ab1cf3da1]]
> >> 1: [./app/x86_64-native-linux-gcc/pktgen(rte_dump_stack+0x2e)
> >> [0x560ab20f105e]]
> >>
> >>
> >>
> >> I searched previous emails but couldn't figure out the problems.
> >>
> >> I would be thankful if you could help me to resolve it.
> >>
> >>
> >> Best regards,
> >> Erfan
> >>
> >>
> >>
> >> --
> >> Erfan Mozaffariahrar, M.Sc.
> >> University of Tuebingen
> >> Faculty of Science
> >> Department of Computer Science
> >> Chair of Communication Networks
> >> Room B309, Sand 13, 72076 Tuebingen, Germany
> >> phone:  (+49)-7071/29-70512
> >> mailto: erfan.mozaffariahrar@uni-tuebingen.de
> >> http://kn.inf.uni-tuebingen.de
> >>
> >>
> >
> > --
> > Rgds,
> > Nishant
>
>
>
> --
> Erfan Mozaffariahrar, M.Sc.
> University of Tuebingen
> Faculty of Science
> Department of Computer Science
> Chair of Communication Networks
> Room B309, Sand 13, 72076 Tuebingen, Germany
> phone:  (+49)-7071/29-70512
> mailto: erfan.mozaffariahrar@uni-tuebingen.de
> http://kn.inf.uni-tuebingen.de
>
>

-- 
Rgds,
Nishant

  reply	other threads:[~2020-07-06 14:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-06 10:18 Erfan Mozaffariahrar
2020-07-06 10:44 ` Nishant Verma
2020-07-06 13:51   ` Erfan Mozaffariahrar
2020-07-06 14:03     ` Nishant Verma [this message]
2020-07-06 14:21       ` Erfan Mozaffariahrar

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=CAHhCjUFaSz-N4T8gxRxDZxo4RoDcUiyLA+M7Sz8gG1gLiyx2Hw@mail.gmail.com \
    --to=vnish11@gmail.com \
    --cc=erfan.mozaffariahrar@uni-tuebingen.de \
    --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).