Go to file
Anatoly Burakov a5ff05d60f mem: support unmapping pages at runtime
This isn't used anywhere yet, but the support is now there. Also,
adding cleanup to allocation procedures, so that if we fail to
allocate everything we asked for, we can free all of it back.

Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
Tested-by: Santosh Shukla <santosh.shukla@caviumnetworks.com>
Tested-by: Hemant Agrawal <hemant.agrawal@nxp.com>
Tested-by: Gowrishankar Muthukrishnan <gowrishankar.m@linux.vnet.ibm.com>
2018-04-11 19:57:20 +02:00
app app/crypto-perf: fix IOVA translation 2018-04-11 02:12:16 +02:00
buildtools
config mem: replace memseg with memseg lists 2018-04-11 19:55:39 +02:00
devtools eal: support strlcpy function 2018-04-04 17:33:08 +02:00
doc mem: replace memseg with memseg lists 2018-04-11 19:55:39 +02:00
drivers memzone: replace memzone array with fbarray 2018-04-11 19:56:30 +02:00
examples examples/ip_pipeline: skip in FreeBSD build 2018-04-10 14:41:01 +02:00
kernel kni: fix build on RHEL 7.5 2018-03-28 00:15:08 +02:00
lib mem: support unmapping pages at runtime 2018-04-11 19:57:20 +02:00
license
mk use SPDX tag for RehiveTech copyright files 2018-04-11 01:47:43 +02:00
pkg version: 18.02.0 2018-02-14 19:11:02 +01:00
test memzone: replace memzone array with fbarray 2018-04-11 19:56:30 +02:00
usertools usertools: change to SPDX license identifier 2018-04-11 01:48:12 +02:00
.gitattributes
.gitignore
GNUmakefile move kernel modules directories 2018-03-21 23:04:21 +01:00
MAINTAINERS maintainers: call out subtree committers 2018-04-11 00:52:51 +02:00
Makefile
meson_options.txt
meson.build move kernel modules directories 2018-03-21 23:04:21 +01:00
README

DPDK is a set of libraries and drivers for fast packet processing.
It supports many processor architectures and both FreeBSD and Linux.

The DPDK uses the Open Source BSD-3-Clause license for the core libraries
and drivers. The kernel components are GPL-2.0 licensed.

Please check the doc directory for release notes,
API documentation, and sample application information.

For questions and usage discussions, subscribe to: users@dpdk.org
Report bugs and issues to the development mailing list: dev@dpdk.org