From: "Rosen, Rami" <rami.rosen@intel.com>
To: RanjithKumar <ranjithdvk@gmail.com>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] I could not execute multi process client server sample application
Date: Fri, 30 Jun 2017 21:05:16 +0000 [thread overview]
Message-ID: <9B0331B6EBBD0E4684FBFAEDA55776F93DA3F980@HASMSX110.ger.corp.intel.com> (raw)
In-Reply-To: <CACxh0QSb02diC0cp22ACDct=_pOk7ZMn0X5d8JdZitEJDDomhg@mail.gmail.com>
Hi Ranjith,
Which network device are you binding ?
DPDK supports over 20 types of nics, listed here:
http://dpdk.org/doc/nics
Do you see your nic (the one that you bind to dpdk, with PCI ID
0000:02:00.0) in this list ?
I would guess that this is Marvell NIC (due to 88E8057 in the output of ./dpdk-devbind.py -s). In the list of DPDK supported NICs there is no NIC from Marvell.
Regards,
Rami Rosen
-----Original Message-----
From: users [mailto:users-bounces@dpdk.org] On Behalf Of RanjithKumar
Sent: Friday, June 30, 2017 14:58
To: users@dpdk.org
Subject: [dpdk-users] I could not execute multi process client server sample application
Hello All,
I have installed DPDK and able to execute the hello world sample application. But i could not execute multi process server client sample application. i am getting below highlighted error while executing server application.
labadmin@labadmin-ThinkCentre-A58:~/dpdk_install_sat/dpdk-stable-17.02.1/examples/multi_process/client_server_mp/mp_server/mp_server/x86_64-native-linuxapp-gcc$
sudo ./mp_server -c 2 -n 4 -- -p 3 -n 1
EAL: Detected 2 lcore(s)
EAL: Probing VFIO support...
EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using unreliable clock cycles !
WARNING: requested port 0 not present - ignoring
WARNING: requested port 1 not present - ignoring
./mp_server [EAL options] -- -p PORTMASK -n NUM_CLIENTS [-s NUM_SOCKETS] -p PORTMASK: hexadecimal bitmask of ports to use -n NUM_CLIENTS: number of client processes to use
*The below is the output of bind status*:
labadmin@labadmin-ThinkCentre-A58:~/dpdk_install_sat/dpdk-stable-17.02.1/usertools$
./dpdk-devbind.py -s
Network devices using DPDK-compatible driver ============================================
0000:02:00.0 '88E8057 PCI-E Gigabit Ethernet Controller' drv=igb_uio unused=
Network devices using kernel driver
===================================
0000:03:04.0 'VT6105/VT6106S [Rhine-III]' if=eth0 drv=via-rhine unused=igb_uio *Active*
Other network devices
=====================
<none>
Crypto devices using DPDK-compatible driver ===========================================
<none>
Crypto devices using kernel driver
==================================
<none>
Other crypto devices
====================
<none>
*The below is CPU layout output:*
labadmin@labadmin-ThinkCentre-A58:~/dpdk_install_sat/dpdk-stable-17.02.1/usertools$
./cpu_layout.py
============================================================
Core and Socket Information (as reported by '/proc/cpuinfo') ============================================================
cores = [0, 1]
sockets = [0]
Socket 0
--------
Core 0 [0]
Core 1 [1]
labadmin@labadmin-ThinkCentre-A58
:~/dpdk_install_sat/dpdk-stable-17.02.1/usertools$
Please let me know if i missed anything.
Regards,
Ranjith
prev parent reply other threads:[~2017-06-30 21:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-30 11:58 RanjithKumar
2017-06-30 21:05 ` Rosen, Rami [this message]
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=9B0331B6EBBD0E4684FBFAEDA55776F93DA3F980@HASMSX110.ger.corp.intel.com \
--to=rami.rosen@intel.com \
--cc=ranjithdvk@gmail.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).