dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 199] Azure DPDK 18.11 Multiple Processes Example Support
Date: Wed, 30 Jan 2019 00:17:36 +0000	[thread overview]
Message-ID: <bug-199-3@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 199
           Summary: Azure DPDK 18.11 Multiple Processes Example Support
           Product: DPDK
           Version: 18.11
          Hardware: x86
                OS: Linux
            Status: CONFIRMED
          Severity: critical
          Priority: Normal
         Component: examples
          Assignee: dev@dpdk.org
          Reporter: sju@paloaltonetworks.com
  Target Milestone: ---

Hi, 

I have a Azure VM with accelerated network enabled with 1 management interface
and 2 data interfaces. 

Following the documents from :
https://docs.microsoft.com/en-us/azure/virtual-network/setup-dpdk


I can successfully run testpmd example with 2 data interfaces. 

The running command of testpmd is:

./testpmd -w b1f0:00:02.0 -w b4b1:00:02.0 --vdev="net_vdev_netvsc0,iface=eth1"
--vdev="net_vdev_netvsc1,iface=eth2"

However, if I try the multiple process version based on
https://doc.dpdk.org/guides/sample_app_ug/multi_process.html, it failed. The
running command is:

./symmetric_mp -w b1f0:00:02.0 -w b4b1:00:02.0
--vdev="net_vdev_netvsc0,iface=eth1" --vdev="net_vdev_netvsc1,iface=eth2"  -l 1
-n 4 --proc-type=auto -- -p 3 --num-procs=4 --proc-id=0 
EAL: Detected 20 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Auto-detected process type: PRIMARY
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: No free hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using unreliable
clock cycles !
EAL: PCI device b1f0:00:02.0 on NUMA socket -1
EAL:   Invalid NUMA socket, default to 0
EAL:   probe driver: 15b3:1004 net_mlx4
PMD: net_mlx4: PCI information matches, using device "mlx4_1" (VF: true)
PMD: net_mlx4: 1 port(s) detected
PMD: net_mlx4: port 1 MAC address is 00:0d:3a:f9:47:24
EAL: PCI device b4b1:00:02.0 on NUMA socket -1
EAL:   Invalid NUMA socket, default to 0
EAL:   probe driver: 15b3:1004 net_mlx4
PMD: net_mlx4: PCI information matches, using device "mlx4_2" (VF: true)
PMD: net_mlx4: 1 port(s) detected
PMD: net_mlx4: port 1 MAC address is 00:0d:3a:f9:48:8b
net_vdev_netvsc: probably using routed NetVSC interface "eth1" (index 3)
rte_pmd_tap_probe(): Initializing pmd_tap for net_tap_vsc0 as dtap0
net_vdev_netvsc: probably using routed NetVSC interface "eth2" (index 4)
rte_pmd_tap_probe(): Initializing pmd_tap for net_tap_vsc1 as dtap1

Checking link statusdone
APP: Finished Process Init.
Lcore 1 has nothing to do


It shows it has nothing to do and quits. I am not sure how to run Azure DPDK
with symmetric_mp.


Could you help me?

Thanks.
Suyang

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

                 reply	other threads:[~2019-01-30  0:17 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-199-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 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).