2 Copyright(c) 2010-2014 Intel Corporation. All rights reserved.
5 Redistribution and use in source and binary forms, with or without
6 modification, are permitted provided that the following conditions
9 * Redistributions of source code must retain the above copyright
10 notice, this list of conditions and the following disclaimer.
11 * Redistributions in binary form must reproduce the above copyright
12 notice, this list of conditions and the following disclaimer in
13 the documentation and/or other materials provided with the
15 * Neither the name of Intel Corporation nor the names of its
16 contributors may be used to endorse or promote products derived
17 from this software without specific prior written permission.
19 THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
20 "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
21 LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
22 A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
23 OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
24 SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
25 LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
26 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
27 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
28 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
29 OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
34 This chapter describes the packages required to compile the DPDK.
38 If the DPDK is being used on an Intel® Communications Chipset 89xx Series platform,
39 please consult the *Intel® Communications Chipset 89xx Series Software for Linux Getting Started Guide*.
41 BIOS Setting Prerequisite on x86
42 --------------------------------
44 For the majority of platforms, no special BIOS settings are needed to use basic DPDK functionality.
45 However, for additional HPET timer and power management functionality,
46 and high performance of small packets on 40G NIC, BIOS setting changes may be needed.
47 Consult the section on :ref:`Enabling Additional Functionality <Enabling_Additional_Functionality>`
48 for more information on the required changes.
50 Compilation of the DPDK
51 -----------------------
57 Testing has been performed using Fedora 18. The setup commands and installed packages needed on other systems may be different.
58 For details on other Linux distributions and the versions tested, please consult the DPDK Release Notes.
62 * coreutils: ``cmp``, ``sed``, ``grep``, ``arch``, etc.
64 * gcc: versions 4.5.x or later is recommended for ``i686/x86_64``. Versions 4.8.x or later is recommended
65 for ``ppc_64`` and ``x86_x32`` ABI. On some distributions, some specific compiler flags and linker flags are enabled by
66 default and affect performance (``-fstack-protector``, for example). Please refer to the documentation
67 of your distribution and to ``gcc -dumpspecs``.
69 * libc headers, often packaged as ``gcc-multilib`` (``glibc-devel.i686`` / ``libc6-dev-i386``;
70 ``glibc-devel.x86_64`` / ``libc6-dev`` for 64-bit compilation on Intel architecture;
71 ``glibc-devel.ppc64`` for 64 bit IBM Power architecture;)
73 * Linux kernel headers or sources required to build kernel modules. (kernel - devel.x86_64;
76 * Additional packages required for 32-bit compilation on 64-bit systems are:
78 * glibc.i686, libgcc.i686, libstdc++.i686 and glibc-devel.i686 for Intel i686/x86_64;
80 * glibc.ppc64, libgcc.ppc64, libstdc++.ppc64 and glibc-devel.ppc64 for IBM ppc_64;
84 x86_x32 ABI is currently supported with distribution packages only on Ubuntu
85 higher than 13.10 or recent Debian distribution. The only supported compiler is gcc 4.8+.
89 Python, version 2.6 or 2.7, to use various helper scripts included in the DPDK package.
94 * Intel® C++ Compiler (icc). For installation, additional libraries may be required.
95 See the icc Installation Guide found in the Documentation directory under the compiler installation.
97 * IBM® Advance ToolChain for Powerlinux. This is a set of open source development tools and runtime libraries
98 which allows users to take leading edge advantage of IBM's latest POWER hardware features on Linux. To install
99 it, see the IBM official installation document.
101 * libpcap headers and libraries (libpcap-devel) to compile and use the libpcap-based poll-mode driver.
102 This driver is disabled by default and can be enabled by setting ``CONFIG_RTE_LIBRTE_PMD_PCAP=y`` in the build time config file.
104 * libarchive headers and library are needed for some unit tests using tar to get their resources.
107 Running DPDK Applications
108 -------------------------
110 To run an DPDK application, some customization may be required on the target machine.
117 * Kernel version >= 2.6.34
119 The kernel version in use can be checked using the command::
123 * glibc >= 2.7 (for features related to cpuset)
125 The version can be checked using the ``ldd --version`` command.
127 * Kernel configuration
129 In the Fedora OS and other common distributions, such as Ubuntu, or Red Hat Enterprise Linux,
130 the vendor supplied kernel configurations can be used to run most DPDK applications.
132 For other kernel builds, options which should be enabled for DPDK include:
138 * PROC_PAGE_MONITOR support
140 * HPET and HPET_MMAP configuration options should also be enabled if HPET support is required.
141 See the section on :ref:`High Precision Event Timer (HPET) Functionality <High_Precision_Event_Timer>` for more details.
143 .. _linux_gsg_hugepages:
145 Use of Hugepages in the Linux Environment
146 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
148 Hugepage support is required for the large memory pool allocation used for packet buffers
149 (the HUGETLBFS option must be enabled in the running kernel as indicated the previous section).
150 By using hugepage allocations, performance is increased since fewer pages are needed,
151 and therefore less Translation Lookaside Buffers (TLBs, high speed translation caches),
152 which reduce the time it takes to translate a virtual page address to a physical page address.
153 Without hugepages, high TLB miss rates would occur with the standard 4k page size, slowing performance.
155 Reserving Hugepages for DPDK Use
156 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
158 The allocation of hugepages should be done at boot time or as soon as possible after system boot
159 to prevent memory from being fragmented in physical memory.
160 To reserve hugepages at boot time, a parameter is passed to the Linux kernel on the kernel command line.
162 For 2 MB pages, just pass the hugepages option to the kernel. For example, to reserve 1024 pages of 2 MB, use::
166 For other hugepage sizes, for example 1G pages, the size must be specified explicitly and
167 can also be optionally set as the default hugepage size for the system.
168 For example, to reserve 4G of hugepage memory in the form of four 1G pages, the following options should be passed to the kernel::
170 default_hugepagesz=1G hugepagesz=1G hugepages=4
174 The hugepage sizes that a CPU supports can be determined from the CPU flags on Intel architecture.
175 If pse exists, 2M hugepages are supported; if pdpe1gb exists, 1G hugepages are supported.
176 On IBM Power architecture, the supported hugepage sizes are 16MB and 16GB.
180 For 64-bit applications, it is recommended to use 1 GB hugepages if the platform supports them.
182 In the case of a dual-socket NUMA system,
183 the number of hugepages reserved at boot time is generally divided equally between the two sockets
184 (on the assumption that sufficient memory is present on both sockets).
186 See the Documentation/kernel-parameters.txt file in your Linux source tree for further details of these and other kernel options.
190 For 2 MB pages, there is also the option of allocating hugepages after the system has booted.
191 This is done by echoing the number of hugepages required to a nr_hugepages file in the ``/sys/devices/`` directory.
192 For a single-node system, the command to use is as follows (assuming that 1024 pages are required)::
194 echo 1024 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages
196 On a NUMA machine, pages should be allocated explicitly on separate nodes::
198 echo 1024 > /sys/devices/system/node/node0/hugepages/hugepages-2048kB/nr_hugepages
199 echo 1024 > /sys/devices/system/node/node1/hugepages/hugepages-2048kB/nr_hugepages
203 For 1G pages, it is not possible to reserve the hugepage memory after the system has booted.
205 Using Hugepages with the DPDK
206 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
208 Once the hugepage memory is reserved, to make the memory available for DPDK use, perform the following steps::
211 mount -t hugetlbfs nodev /mnt/huge
213 The mount point can be made permanent across reboots, by adding the following line to the ``/etc/fstab`` file::
215 nodev /mnt/huge hugetlbfs defaults 0 0
217 For 1GB pages, the page size must be specified as a mount option::
219 nodev /mnt/huge_1GB hugetlbfs pagesize=1GB 0 0
221 Xen Domain0 Support in the Linux Environment
222 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
224 The existing memory management implementation is based on the Linux kernel hugepage mechanism.
225 On the Xen hypervisor, hugepage support for DomainU (DomU) Guests means that DPDK applications work as normal for guests.
227 However, Domain0 (Dom0) does not support hugepages.
228 To work around this limitation, a new kernel module rte_dom0_mm is added to facilitate the allocation and mapping of memory via
229 **IOCTL** (allocation) and **MMAP** (mapping).
231 Enabling Xen Dom0 Mode in the DPDK
232 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
234 By default, Xen Dom0 mode is disabled in the DPDK build configuration files.
235 To support Xen Dom0, the CONFIG_RTE_LIBRTE_XEN_DOM0 setting should be changed to “y”, which enables the Xen Dom0 mode at compile time.
237 Furthermore, the CONFIG_RTE_EAL_ALLOW_INV_SOCKET_ID setting should also be changed to “y” in the case of the wrong socket ID being received.
239 Loading the DPDK rte_dom0_mm Module
240 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
242 To run any DPDK application on Xen Dom0, the ``rte_dom0_mm`` module must be loaded into the running kernel with rsv_memsize option.
243 The module is found in the kmod sub-directory of the DPDK target directory.
244 This module should be loaded using the insmod command as shown below (assuming that the current directory is the DPDK target directory)::
246 sudo insmod kmod/rte_dom0_mm.ko rsv_memsize=X
248 The value X cannot be greater than 4096(MB).
250 Configuring Memory for DPDK Use
251 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
253 After the rte_dom0_mm.ko kernel module has been loaded, the user must configure the memory size for DPDK usage.
254 This is done by echoing the memory size to a memsize file in the /sys/devices/ directory.
255 Use the following command (assuming that 2048 MB is required)::
257 echo 2048 > /sys/kernel/mm/dom0-mm/memsize-mB/memsize
259 The user can also check how much memory has already been used::
261 cat /sys/kernel/mm/dom0-mm/memsize-mB/memsize_rsvd
263 Xen Domain0 does not support NUMA configuration, as a result the ``--socket-mem`` command line option is invalid for Xen Domain0.
267 The memsize value cannot be greater than the rsv_memsize value.
269 Running the DPDK Application on Xen Domain0
270 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
272 To run the DPDK application on Xen Domain0, an extra command line option ``--xen-dom0`` is required.