DPDK usage discussions
 help / color / mirror / Atom feed
From: Marco Kwok <maruko.kwok@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Cannot run Quick Start on ubuntu16.04.1 VM
Date: Thu, 29 Dec 2016 14:25:29 +0800	[thread overview]
Message-ID: <CAE56PLs-9noc8LxnfFmeSarxo-n4szNk6O-qVnPtBDEYeez3dw@mail.gmail.com> (raw)

Hello all,

I am running vmware workstation for ubuntu 16.04.1.
Following the guide here:
http://dpdk.org/doc/quick-start

everything is fine until this line:

> echo 64 > /sys/devices/system/node/node0/hugepages/hugepages-
> 2048kB/nr_hugepages

I got permission denied even with sudo, so I get through it with:

> sh -c "echo 64 > /sys/devices/system/node/node0/hugepages/hugepages-
> 2048kB/nr_hugepages"


Then I want to start the program testpmd and I found the argument of this
line is not supported:

> -i --nb-cores=2 --nb-ports=2 --total-num-mbufs=2048


With this command to start the testpmd(my card is not eth0 and eth1 but
ens33 and 38 instead):
sudo build/app/testpmd -c7 -n3 --vdev=eth_pcap0,iface=ens33
--vdev=eth_pcap1,iface=ens38

EAL: Detected 4 lcore(s)
>
> EAL: No free hugepages reported in hugepages-1048576kB
>
> EAL: Probing VFIO support...
>
> PMD: Initializing pmd_pcap for eth_pcap0
>
> PMD: Creating pcap-backed ethdev on numa socket 0
>
> PMD: Initializing pmd_pcap for eth_pcap1
>
> PMD: Creating pcap-backed ethdev on numa socket 0
>
> PMD: bnxt_rte_pmd_init() called for (null)
>
> EAL: PCI device 0000:02:01.0 on NUMA socket -1
>
> EAL:   probe driver: 8086:100f rte_em_pmd
>
> EAL: PCI device 0000:02:06.0 on NUMA socket -1
>
> EAL:   probe driver: 8086:100f rte_em_pmd
>
> USER1: create a new mbuf pool <mbuf_pool_socket_0>: n=163456, size=2176,
>> socket=0
>
> EAL: Error - exiting with code: 1
>
>   Cause: Creation of mbuf pool for socket 0 failed: Cannot allocate memory
>
>
Does anybody know how I could get through this?

Best Regards,
Mark

                 reply	other threads:[~2016-12-29  6:25 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=CAE56PLs-9noc8LxnfFmeSarxo-n4szNk6O-qVnPtBDEYeez3dw@mail.gmail.com \
    --to=maruko.kwok@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).