DPDK usage discussions
 help / color / mirror / Atom feed
From: Paul Tsvika <mozloverinweb@gmail.com>
To: users@dpdk.org
Subject: Re: [dpdk-users] Run testpmd application and encountered no free page issues
Date: Sat, 17 Jun 2017 23:46:44 +0800	[thread overview]
Message-ID: <CAGi_MX=H0zYMEsp4MXQhZ8W+=VvKgPC9EwNO5bs7pYb7DUmRpQ@mail.gmail.com> (raw)
In-Reply-To: <CAGi_MX=S7LK9qf1fhO5HqjrV847Siz7CnZ1VGVf_zWfDLAjNnw@mail.gmail.com>

Anyone,

or my question is not clear enough ?



Thanks




Paul

2017-06-16 18:20 GMT+08:00 Paul Tsvika <mozloverinweb@gmail.com>:

> Hi,
>
> I have one board with two 10G etherent on it. ( and two 1G ethernet as
> well )
>
> Below is my working environment:
>
> OS: Ubuntu 16.04
> 10G Ethernet controller: X552/X557-AT 10GBASE-T
> Ethernet driver: ixgbe - 4.2.1-k
> dpdk version: 17.02.1
>
> In order to avoid doing configuration incorrectly, i run the dpdk-setup.sh
> in the directory usertools.
>
> Press enter to continue ...
> ----------------------------------------------------------
>  Step 1: Select the DPDK environment to build
> ----------------------------------------------------------
> [1] arm64-armv8a-linuxapp-gcc
> [2] arm64-dpaa2-linuxapp-gcc
> [3] arm64-thunderx-linuxapp-gcc
> [4] arm64-xgene1-linuxapp-gcc
> [5] arm-armv7a-linuxapp-gcc
> [6] i686-native-linuxapp-gcc
> [7] i686-native-linuxapp-icc
> [8] ppc_64-power8-linuxapp-gcc
> [9] tile-tilegx-linuxapp-gcc
> [10] x86_64-native-bsdapp-clang
> [11] x86_64-native-bsdapp-gcc
> [12] x86_64-native-linuxapp-clang
> [13] x86_64-native-linuxapp-gcc
> [14] x86_64-native-linuxapp-icc
> [15] x86_x32-native-linuxapp-gcc
>
> ----------------------------------------------------------
>  Step 2: Setup linuxapp environment
> ----------------------------------------------------------
> [16] Insert IGB UIO module
> [17] Insert VFIO module
> [18] Insert KNI module
> [19] Setup hugepage mappings for non-NUMA systems
> [20] Setup hugepage mappings for NUMA systems
> [21] Display current Ethernet/Crypto device settings
> [22] Bind Ethernet/Crypto device to IGB UIO module
> [23] Bind Ethernet/Crypto device to VFIO module
> [24] Setup VFIO permissions
>
> ----------------------------------------------------------
>  Step 3: Run test application for linuxapp environment
> ----------------------------------------------------------
> [25] Run test application ($RTE_TARGET/app/test)
> [26] Run testpmd application in interactive mode ($RTE_TARGET/app/testpmd)
>
> ----------------------------------------------------------
>  Step 4: Other tools
> ----------------------------------------------------------
> [27] List hugepage info from /proc/meminfo
>
> ----------------------------------------------------------
>  Step 5: Uninstall and system cleanup
> ----------------------------------------------------------
> [28] Unbind devices from IGB UIO or VFIO driver
> [29] Remove IGB UIO module
> [30] Remove VFIO module
> [31] Remove KNI module
> [32] Remove hugepage mappings
>
> [33] Exit Script
>
> *Option: 19*
>
> Removing currently reserved hugepages
> Unmounting /mnt/huge and removing directory
>
>   Input the number of 2048kB hugepages
>   Example: to have 128MB of hugepages available in a 2MB huge page system,
>   enter '64' to reserve 64 * 2MB pages
> Number of pages: 64
> Reserving hugepages
> Creating /mnt/huge and mounting as hugetlbfs
>
> Press enter to continue ...
> ----------------------------------------------------------
>  Step 1: Select the DPDK environment to build
> ----------------------------------------------------------
> [1] arm64-armv8a-linuxapp-gcc
> [2] arm64-dpaa2-linuxapp-gcc
> [3] arm64-thunderx-linuxapp-gcc
> [4] arm64-xgene1-linuxapp-gcc
> [5] arm-armv7a-linuxapp-gcc
> [6] i686-native-linuxapp-gcc
> [7] i686-native-linuxapp-icc
> [8] ppc_64-power8-linuxapp-gcc
> [9] tile-tilegx-linuxapp-gcc
> [10] x86_64-native-bsdapp-clang
> [11] x86_64-native-bsdapp-gcc
> [12] x86_64-native-linuxapp-clang
> [13] x86_64-native-linuxapp-gcc
> [14] x86_64-native-linuxapp-icc
> [15] x86_x32-native-linuxapp-gcc
>
> ----------------------------------------------------------
>  Step 2: Setup linuxapp environment
> ----------------------------------------------------------
> [16] Insert IGB UIO module
> [17] Insert VFIO module
> [18] Insert KNI module
> [19] Setup hugepage mappings for non-NUMA systems
> [20] Setup hugepage mappings for NUMA systems
> [21] Display current Ethernet/Crypto device settings
> [22] Bind Ethernet/Crypto device to IGB UIO module
> [23] Bind Ethernet/Crypto device to VFIO module
> [24] Setup VFIO permissions
>
> ----------------------------------------------------------
>  Step 3: Run test application for linuxapp environment
> ----------------------------------------------------------
> [25] Run test application ($RTE_TARGET/app/test)
> [26] Run testpmd application in interactive mode ($RTE_TARGET/app/testpmd)
>
> ----------------------------------------------------------
>  Step 4: Other tools
> ----------------------------------------------------------
> [27] List hugepage info from /proc/meminfo
>
> ----------------------------------------------------------
>  Step 5: Uninstall and system cleanup
> ----------------------------------------------------------
> [28] Unbind devices from IGB UIO or VFIO driver
> [29] Remove IGB UIO module
> [30] Remove VFIO module
> [31] Remove KNI module
> [32] Remove hugepage mappings
>
> [33] Exit Script
>
> *Option: 26*
>
>
>   Enter hex bitmask of cores to execute testpmd app on
>   Example: to execute app on cores 0 to 7, enter 0xff
> bitmask: 0xff
> Launching app
> EAL: Detected 16 lcore(s)
> EAL: No free hugepages reported in hugepages-1048576kB
> EAL: Probing VFIO support...
> EAL: PCI device 0000:03:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:15ad net_ixgbe
> EAL: PCI device 0000:03:00.1 on NUMA socket 0
> EAL:   probe driver: 8086:15ad net_ixgbe
> EAL: PCI device 0000:05:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:1521 net_e1000_igb
> EAL: PCI device 0000:05:00.1 on NUMA socket 0
> EAL:   probe driver: 8086:1521 net_e1000_igb
> EAL: No probed ethernet devices
> Interactive-mode selected
> USER1: create a new mbuf pool <mbuf_pool_socket_0>: n=203456, size=2176,
> socket=0
> EAL: Error - exiting with code: 1
>   Cause: Creation of mbuf pool for socket 0 failed: Cannot allocate memory
>
>
> Is there anything I might not do right ?
>
> Your reply is appreciated.
>
>
>
> Paul
>
> --
> P.T
>



-- 
P.T

  reply	other threads:[~2017-06-17 15:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-16 10:20 Paul Tsvika
2017-06-17 15:46 ` Paul Tsvika [this message]
2017-06-19  5:49   ` Shreyansh Jain
2017-06-19  6:08     ` Paul Tsvika
2017-06-19  8:39       ` Shreyansh Jain
2017-06-20  8:57         ` Paul Tsvika
2017-06-20 11:10           ` Shreyansh Jain
2017-06-21  3:16             ` Paul Tsvika
2017-06-21  4:40               ` Muhammad Zain-ul-Abideen
2017-06-21  5:35               ` Shreyansh Jain
2017-06-21  7:49                 ` Paul Tsvika

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='CAGi_MX=H0zYMEsp4MXQhZ8W+=VvKgPC9EwNO5bs7pYb7DUmRpQ@mail.gmail.com' \
    --to=mozloverinweb@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).