d/numam-dpdk
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
2a5d547a4a
numam-dpdk/MAINTAINERS

1632 lines
43 KiB
Plaintext
Raw Normal View History

maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
DPDK Maintainers
================
The intention of this file is to provide a set of names that we can rely on
for helping in patch reviews and questions.
These names are additional recipients for emails sent to dev@dpdk.org.
Please avoid private emails.
Descriptions of section entries:
M: Maintainer's Full Name <address@domain>
T: Git tree location.
F: Files and directories with wildcard patterns.
A trailing slash includes all files and subdirectory files.
A wildcard includes all files but not subdirectories.
One pattern per line. Multiple F: lines acceptable.
X: Files and directories exclusion, same rules as F:
K: Keyword regex pattern to match content.
One regex pattern per line. Multiple K: lines acceptable.
General Project Administration
------------------------------
maintainers: separate main tree and devtools maintenance Being the maintainer of devtools is different of maintaining the main tree. Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
2017-09-19 15:48:48 +00:00
Main Branch
maintainers: update email address Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
2017-04-18 21:36:51 +00:00
M: Thomas Monjalon <thomas@monjalon.net>
maintainers: add David for main branch David will be co-maintaining the top level tree with Thomas, Welcome and best luck J Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2019-09-26 10:12:55 +00:00
M: David Marchand <david.marchand@redhat.com>
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
T: git://dpdk.org/dpdk
maintainers: call out subtree committers The MAINTAINERS file contains information of the maintainers of the different components on DPDK. However, it does not give any information on who maintains the different subtrees which accept new commits for these components. This commit adds a list of the subtree committers. Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-03-28 19:30:40 +00:00
Next-net Tree
M: Ferruh Yigit <ferruh.yigit@intel.com>
maintainers: add Andrew for next-net tree Adding Andrew as co-maintainer to next-net sub-tree. Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Andrew Rybchenko <arybchenko@solarflare.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2019-07-17 17:50:20 +00:00
M: Andrew Rybchenko <arybchenko@solarflare.com>
maintainers: call out subtree committers The MAINTAINERS file contains information of the maintainers of the different components on DPDK. However, it does not give any information on who maintains the different subtrees which accept new commits for these components. This commit adds a list of the subtree committers. Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-03-28 19:30:40 +00:00
T: git://dpdk.org/next/dpdk-next-net
maintainers: add next-net-brcm sub-tree Adding vendor specific sub-tree for Broadcom drivers. The next-net-brcm sub-tree will be sub-tree of the next-net. Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2019-10-15 07:38:00 +00:00
Next-net-brcm Tree
M: Ajit Khaparde <ajit.khaparde@broadcom.com>
T: git://dpdk.org/next/dpdk-next-net-brcm
maintainers: call out subtree committers The MAINTAINERS file contains information of the maintainers of the different components on DPDK. However, it does not give any information on who maintains the different subtrees which accept new commits for these components. This commit adds a list of the subtree committers. Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-03-28 19:30:40 +00:00
Next-net-intel Tree
maintainers: update dpdk-next-net-intel Xiaolong Ye will replace Beilei Xing as co-maintainer of dpdk-next-net-intel. Signed-off-by: Qi Zhang <qi.z.zhang@intel.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
2019-06-19 08:24:12 +00:00
M: Xiaolong Ye <xiaolong.ye@intel.com>
maintainers: adjust maintainership of Intel tree Currently I am the main committer of dpdk-next-net-intel tree. Signed-off-by: Xiaolong Ye <xiaolong.ye@intel.com> Acked-by: Qi Zhang <qi.z.zhang@intel.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
2019-12-11 09:12:35 +00:00
M: Qi Zhang <qi.z.zhang@intel.com>
maintainers: call out subtree committers The MAINTAINERS file contains information of the maintainers of the different components on DPDK. However, it does not give any information on who maintains the different subtrees which accept new commits for these components. This commit adds a list of the subtree committers. Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-03-28 19:30:40 +00:00
T: git://dpdk.org/next/dpdk-next-net-intel
maintainers: claim maintainership of net-mrvl sub-tree Claim the maintainership of the sub tree dpdk-next-net-mrvl, which covers all the Marvell network PMDs. Signed-off-by: Jerin Jacob <jerinj@marvell.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2019-06-25 05:42:41 +00:00
Next-net-mrvl Tree
M: Jerin Jacob <jerinj@marvell.com>
T: git://dpdk.org/next/dpdk-next-net-mrvl
maintainers: call out subtree committers The MAINTAINERS file contains information of the maintainers of the different components on DPDK. However, it does not give any information on who maintains the different subtrees which accept new commits for these components. This commit adds a list of the subtree committers. Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-03-28 19:30:40 +00:00
Next-net-mlx Tree
maintainers: update for Mellanox Due to position change, cannot be a full time maintainer anymore. The git tree dpdk-next-net-mlx will be managed by Raslan, as approved by the DPDK Technical Board. For mlx5 PMD, Slava is added as additional maintainer. Will continue to be involved in the DPDK community in different ways. Signed-off-by: Shahaf Shuler <shahafs@mellanox.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
2019-07-04 10:01:04 +00:00
M: Raslan Darawsheh <rasland@mellanox.com>
maintainers: call out subtree committers The MAINTAINERS file contains information of the maintainers of the different components on DPDK. However, it does not give any information on who maintains the different subtrees which accept new commits for these components. This commit adds a list of the subtree committers. Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-03-28 19:30:40 +00:00
T: git://dpdk.org/next/dpdk-next-net-mlx
Next-virtio Tree
maintainers: fix typo and ordering Fix logical/alphabetical ordering, spacing, and syntax typo. Fixes: 8fb3b2576025 ("maintainers: call out subtree committers") Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2018-04-23 01:18:35 +00:00
M: Maxime Coquelin <maxime.coquelin@redhat.com>
maintainers: call out subtree committers The MAINTAINERS file contains information of the maintainers of the different components on DPDK. However, it does not give any information on who maintains the different subtrees which accept new commits for these components. This commit adds a list of the subtree committers. Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-03-28 19:30:40 +00:00
T: git://dpdk.org/next/dpdk-next-virtio
Next-crypto Tree
maintainers: add backup for next-crypto tree Signed-off-by: Akhil Goyal <akhil.goyal@nxp.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2018-04-12 08:32:16 +00:00
M: Akhil Goyal <akhil.goyal@nxp.com>
maintainers: call out subtree committers The MAINTAINERS file contains information of the maintainers of the different components on DPDK. However, it does not give any information on who maintains the different subtrees which accept new commits for these components. This commit adds a list of the subtree committers. Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-03-28 19:30:40 +00:00
T: git://dpdk.org/next/dpdk-next-crypto
Next-eventdev Tree
maintainers: update Cavium email ids Following Marvell's acquisition of Cavium, we need to update all the Cavium maintainer's entries to point to our new e-mail addresses. Update maintainers as they are no longer working for Cavium. Thanks to Harish Patil for his support and development of our various dpdk drivers. Signed-off-by: Jerin Jacob <jerinj@marvell.com>
2018-12-16 15:43:25 +00:00
M: Jerin Jacob <jerinj@marvell.com>
maintainers: call out subtree committers The MAINTAINERS file contains information of the maintainers of the different components on DPDK. However, it does not give any information on who maintains the different subtrees which accept new commits for these components. This commit adds a list of the subtree committers. Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-03-28 19:30:40 +00:00
T: git://dpdk.org/next/dpdk-next-eventdev
Next-qos Tree
M: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
T: git://dpdk.org/next/dpdk-next-qos
Next-pipeline Tree
M: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
T: git://dpdk.org/next/dpdk-next-pipeline
maintainers: add an entry for the stable branches This git tree will be used to backport some fixes from the master branch to maintain some "stable releases". The minor version number z will be incremented for these releases: YY.MM.z Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com> Acked-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
2016-07-25 12:56:37 +00:00
Stable Branches
maintainers: update for stable branches I am maintaining 16.11 until November 2018 Signed-off-by: Luca Boccassi <bluca@debian.org>
2018-02-13 23:31:07 +00:00
M: Luca Boccassi <bluca@debian.org>
maintainers: update for stable branches Yuanhan is no longer maintaining DPDK stable. Add myself as a stable maintainer. Signed-off-by: Kevin Traynor <ktraynor@redhat.com> Acked-by: Luca Boccassi <bluca@debian.org> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2019-09-05 15:49:44 +00:00
M: Kevin Traynor <ktraynor@redhat.com>
maintainers: add an entry for the stable branches This git tree will be used to backport some fixes from the master branch to maintain some "stable releases". The minor version number z will be incremented for these releases: YY.MM.z Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: John McNamara <john.mcnamara@intel.com> Acked-by: Yuanhan Liu <yuanhan.liu@linux.intel.com>
2016-07-25 12:56:37 +00:00
T: git://dpdk.org/dpdk-stable
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
Security Issues
M: maintainers@dpdk.org
Documentation (with overlaps)
maintainers: claim responsibility for docs Signed-off-by: John McNamara <john.mcnamara@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-05-13 13:08:28 +00:00
M: John McNamara <john.mcnamara@intel.com>
maintainers: claim co-maintainership of docs Signed-off-by: Marko Kovacevic <marko.kovacevic@intel.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2017-12-05 15:22:07 +00:00
M: Marko Kovacevic <marko.kovacevic@intel.com>
doc: add readme file This project is missing a proper README which is used in other projects and some git visualization services. Only a starting point, please feel free to edit. To keep the file short and current, I avoided putting any specific information about features and versions. Signed-off-by: Stephen Hemminger <stephen@networkplumber.org> Acked-by: John McNamara <john.mcnamara@intel.com>
2015-12-02 04:20:05 +00:00
F: README
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: doc/
maintainers: separate main tree and devtools maintenance Being the maintainer of devtools is different of maintaining the main tree. Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
2017-09-19 15:48:48 +00:00
Developers and Maintainers Tools
M: Thomas Monjalon <thomas@monjalon.net>
F: MAINTAINERS
F: devtools/check-dup-includes.sh
F: devtools/check-maintainers.sh
devtools: move awk script ckecking forbidden tokens The awk code previously read inline in checkpatches.sh was using -d which is a bash option, while bash is not the default shell in all distributions. Now moved to be read from a separate file. Signed-off-by: Arnon Warshavsky <arnon@qwilt.com> Acked-by: Andrzej Ostruszka <amo@semihalf.com>
2018-09-27 09:04:08 +00:00
F: devtools/check-forbidden-tokens.awk
maintainers: separate main tree and devtools maintenance Being the maintainer of devtools is different of maintaining the main tree. Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
2017-09-19 15:48:48 +00:00
F: devtools/check-git-log.sh
F: devtools/check-includes.sh
devtools: check orphan symbols in map files The script check-symbol-maps.sh finds the symbols exported in a map file but not referenced in the codebase. Suggested-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
2018-05-27 21:54:47 +00:00
F: devtools/check-symbol-maps.sh
maintainers: separate main tree and devtools maintenance Being the maintainer of devtools is different of maintaining the main tree. Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
2017-09-19 15:48:48 +00:00
F: devtools/checkpatches.sh
devtools: add script to get maintainers from patch This is a wrapper to Linux kernel get_maintainer.pl file and only supports parsing MAINTAINERS file (no git fallback etc..) Requires DPDK_GETMAINTAINER_PATH devel config option set, please check devtools/load-devel-config. DPDK_GETMAINTAINER_PATH should be full path to the get_maintainer.pl script, like: DPDK_GETMAINTAINER_PATH=~/linux/scripts/get_maintainer.pl Can be used individually: ./devtools/get-maintainer.sh <my.patch> Or via git send-email, to add maintainers automatically: git send-email --to-cmd ./devtools/get-maintainer.sh \ --cc dev@dpdk.org HEAD -4 Currently there is an ugly workaround to be able to use Linux script out of the kernel tree, later better method can replace it. Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
2017-08-04 14:01:25 +00:00
F: devtools/get-maintainer.sh
maintainers: separate main tree and devtools maintenance Being the maintainer of devtools is different of maintaining the main tree. Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
2017-09-19 15:48:48 +00:00
F: devtools/git-log-fixes.sh
F: devtools/load-devel-config
F: devtools/test-build.sh
devtools: add test script for meson builds To simplify testing with the meson and ninja builds, we can add a script to set up and do multiple builds. Currently this script sets up: * clang and gcc builds * builds using static and shared linkage for binaries (libs are always built as both) * a build using the lowest instruction-set level for x86 (-march=nehalem) * cross-builds for each cross-file listed in config/arm Each build is configured in a directory ending in *-build, and then for the build stage, we just call ninja in each directory in turn. [i.e. we assume every directory starting with "build-" is a meson build, which is probably an ok assumption]. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
2018-05-29 14:42:43 +00:00
F: devtools/test-meson-builds.sh
devtools: export dictionary for commit title check Moved title syntax to a separate file so that it improves code readability and allows easy addition. Also logic changed from checking for bad pattern to checking good pattern which documents the expected syntax more clearly, and does not have gaps in the checks. Signed-off-by: Sean Morrissey <sean.morrissey@intel.com> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
2020-02-24 15:30:01 +00:00
F: devtools/words-case.txt
license: introduce SPDX identifiers The DPDK uses the Open Source BSD-3-Clause license for the core libraries and drivers. The kernel components are naturally GPLv2 licensed. Many of the files in the DPDK source code contain the full text of the applicable license. For example, most of the BSD-3-Clause files contain a full copy of the BSD-3-Clause license text. Including big blocks of License headers in all files blows up the source code with mostly redundant information. An additional problem is that even the same licenses are referred to by a number of slightly varying text blocks (full, abbreviated, different indentation, line wrapping and/or white space, with obsolete address information, ...) which makes validation and automatic processing a nightmare. To make this easier, DPDK uses of a single line reference to Unique License Identifiers in source files as defined by the Linux Foundation's SPDX project https://spdk.org. Adding license information in this fashion, rather than adding full license text, can be more efficient for developers; decreases errors; and improves automated detection of licenses. The current set of valid, predefined SPDX identifiers is set forth on the SPDX License List at https://spdx.org/licenses/. For example, to label a file as subject to the BSD-3-Clause license, the following text would be used as the top line of the file. SPDX-License-Identifier: BSD-3-Clause Note: Any new file contributions in DPDK shall adhere to the above scheme. It is also recommended to replace or at least amend the existing license text in the code with SPDX-License-Identifiers. Any exception to DPDK IP policies shall be approved by DPDK tech board and DPDK Governing Board. Steps for any exception approval: 1. Mention the appropriate license identifier form SPDX. If the license is not listed in SPDX Licenses. It is the submitters responsibiliity to get it first listed. 2. Get the required approval from the DPDK Technical Board. Technical board may advise the author to check alternate means first. If no other alternatives are found and the merit of the contributions are important for DPDK's mission, it may decide on such exception with two-thirds vote of the members. 3. Technical board then approach Governing board for such limited approval for the given contribution only. Any approvals shall be documented in "licenses/exceptions.txt" with record dates. Note: From the legal point of view, this patch is supposed to be only a change to the textual representation of the license information, but in no way any change to the actual license terms. With this patch applied, all files will still be licensed under the same terms they were before. Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com> Acked-by: Stephen Hemminger <stephen@networkplumber.org> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2017-12-19 10:14:38 +00:00
F: license/
devtools: add EditorConfig file EditorConfig is a file format and collection of text editor plugins for maintaining consistent coding styles between different editors and IDEs. Initialize the file following the coding rules in doc/guides/contributing/coding_style.rst, doc/guides/contributing/documentation.rst and doc/guides/contributing/patches.rst. In order for this file to be taken into account (unless they use an editor with built-in EditorConfig support), developers will have to install a plugin. Note: The max_line_length property is only supported by a limited number of EditorConfig plugins. It will be ignored if unsupported. Add this new file in MAINTAINERS in the "Developers and Maintainers Tools" section. Link: https://editorconfig.org/ Link: https://github.com/editorconfig/editorconfig-emacs Link: https://github.com/editorconfig/editorconfig-vim Link: https://github.com/editorconfig/editorconfig/wiki/EditorConfig-Properties#max_line_length Signed-off-by: Robin Jarry <robin.jarry@6wind.com>
2019-10-25 14:04:10 +00:00
F: .editorconfig
maintainers: separate main tree and devtools maintenance Being the maintainer of devtools is different of maintaining the main tree. Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
2017-09-19 15:48:48 +00:00
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
Build System
------------
maintainers: update email address Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
2017-04-18 21:36:51 +00:00
M: Thomas Monjalon <thomas@monjalon.net>
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: GNUmakefile
F: Makefile
F: config/
F: mk/
scripts: move to buildtools There is already a directory buildtools for pmdinfogen used by the build system. The scripts used in makefiles are moved here. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Tested-by: Ferruh Yigit <ferruh.yigit@intel.com>
2016-12-15 21:46:47 +00:00
F: buildtools/auto-config-h.sh
F: buildtools/gen-build-mk.sh
F: buildtools/gen-config-h.sh
F: buildtools/relpath.sh
maintainers: dispatch more doc Documentation of build system, EAL and ring lib should be covered by the maintainers of the respective areas. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Olivier Matz <olivier.matz@6wind.com>
2015-02-04 08:08:45 +00:00
F: doc/build-sdk-quick.txt
F: doc/guides/prog_guide/build_app.rst
F: doc/guides/prog_guide/dev_kit_*
F: doc/guides/prog_guide/ext_app_lib_make_help.rst
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
build: add infrastructure for meson and ninja builds To build with meson and ninja, we need some initial infrastructure in place. The build files for meson always need to be called "meson.build", and options get placed in meson_options.txt This commit adds a top-level meson.build file, which sets up the global variables for tracking drivers, libraries, etc., and then includes other build files, before finishing by writing the global build configuration header file and a DPDK pkgconfig file at the end, using some of those same globals. From the top level build file, the only include file thus far is for the config folder, which does some other setup of global configuration parameters, including pulling in architecture specific parameters from an architectural subdirectory. A number of configuration build options are provided for the project to tune a number of global variables which will be used later e.g. max numa nodes, max cores, etc. These settings all make their way to the global build config header "rte_build_config.h". There is also a file "rte_config.h", which includes "rte_build_config.h", and this file is meant to hold other build-time values which are present in our current static build configuration but are not normally meant for user-configuration. Ideally, over time, the values placed here should be moved to the individual libraries or drivers which want those values. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Reviewed-by: Harry van Haaren <harry.van.haaren@intel.com> Acked-by: Keith Wiles <keith.wiles@intel.com> Acked-by: Luca Boccassi <luca.boccassi@gmail.com>
2017-08-28 10:57:12 +00:00
Meson build
M: Bruce Richardson <bruce.richardson@intel.com>
F: meson.build
F: meson_options.txt
F: config/rte_config.h
doc: rebuild with meson whenever a file changes Add proper support for calling sphinx whenever a file in the doc directory changes. This is accomplished by using a wrapper script for sphinx, which runs sphinx but also emits a gcc-format dependency file listing all the doc files. This is used by ninja so that any change to the doc files triggers a rebuild of the docs. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: Aaron Conole <aconole@redhat.com> Acked-by: Luca Boccassi <bluca@debian.org>
2020-01-10 21:52:04 +00:00
F: buildtools/call-sphinx-build.py
buildtools: build with meson Add the buildtools folder, and more specifically the pmdinfogen binary to the meson and ninja build. This will be needed for building the PMDs in the driver folder later, as the pmd info output from the tool needs to be included in those libs. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Reviewed-by: Harry van Haaren <harry.van.haaren@intel.com> Acked-by: Keith Wiles <keith.wiles@intel.com> Acked-by: Luca Boccassi <luca.boccassi@gmail.com>
2017-08-29 13:39:32 +00:00
F: buildtools/gen-pmdinfo-cfile.sh
build: allow using wildcards to disable drivers Rather than having to explicitly list each and every driver to disable in a build, we can use a small python script and the python glob library to expand out the wildcards. This means that we can configure meson using e.g. meson -Ddisable_drivers=crypto/*,event/* build to do a build omitting all the crypto and event drivers. Explicitly specified drivers e.g. net/i40e, work as before, and can be mixed with wildcarded drivers as required. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Reviewed-by: Robin Jarry <robin.jarry@6wind.com> Acked-by: Luca Boccassi <bluca@debian.org>
2020-01-27 14:28:22 +00:00
F: buildtools/list-dir-globs.py
maintainers: add Windows exports script A script used with meson was missing in the list of files. Fixes: 4c773788e05a ("build: generate Windows exports file") Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Reviewed-by: David Marchand <david.marchand@redhat.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2019-06-13 14:11:55 +00:00
F: buildtools/map_to_def.py
build: symlink drivers to library directory With the introduction of bus drivers, we now have a situation where driver libraries will start to depend upon each other. Because of this, the driver libs need to be discoverable by the dynamic loader. There are three options to fix this: 1. Force the user to put the $libdir/dpdk/drivers folder into their library path. 2. Move all libraries from drivers sub-directory to $libdir. 3. Symlink all libraries from the subfolder to the main library dir. Option 1 is not great for usability or distro packaging, and option 2 means that we can't have EAL load all drivers from a known path automatically (as it would error out on non-PMD libs), so option 3 was chosen as the best fix. The only downside is that on a "ninja uninstall" the symlinks are not removed, as they are unknown to meson/ninja. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: Luca Boccassi <bluca@debian.org>
2017-12-06 10:45:48 +00:00
F: buildtools/symlink-drivers-solibs.sh
build: add infrastructure for meson and ninja builds To build with meson and ninja, we need some initial infrastructure in place. The build files for meson always need to be called "meson.build", and options get placed in meson_options.txt This commit adds a top-level meson.build file, which sets up the global variables for tracking drivers, libraries, etc., and then includes other build files, before finishing by writing the global build configuration header file and a DPDK pkgconfig file at the end, using some of those same globals. From the top level build file, the only include file thus far is for the config folder, which does some other setup of global configuration parameters, including pulling in architecture specific parameters from an architectural subdirectory. A number of configuration build options are provided for the project to tune a number of global variables which will be used later e.g. max numa nodes, max cores, etc. These settings all make their way to the global build config header "rte_build_config.h". There is also a file "rte_config.h", which includes "rte_build_config.h", and this file is meant to hold other build-time values which are present in our current static build configuration but are not normally meant for user-configuration. Ideally, over time, the values placed here should be moved to the individual libraries or drivers which want those values. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Reviewed-by: Harry van Haaren <harry.van.haaren@intel.com> Acked-by: Keith Wiles <keith.wiles@intel.com> Acked-by: Luca Boccassi <luca.boccassi@gmail.com>
2017-08-28 10:57:12 +00:00
ci: introduce Travis builds for GitHub repositories GitHub is a service used by developers to store repositories. GitHub provides service integrations that allow 3rd party services to access developer repositories and perform actions. One of these services is Travis-CI, a simple continuous integration platform. This series introduces the ability for any github mirrors of the DPDK project, including developer mirrors, to kick off builds under the travis CI infrastructure. For now, this just means compilation - no other kinds of automated run exists yet. In the future, this can be expanded to execute and report results for any test-suites that might exist. This is a simple initial implementation of a travis build for the DPDK project. It doesn't require any changes from individual developers to enable, but will allow those developers who opt-in to GitHub and the travis service to get automatic builds for every push they make. The files added under .ci/ exist so that in the future, other CI support platforms (such as cirrus, appveyor, etc.) could have a common place to put their requisite scripts without polluting the main tree. Signed-off-by: Aaron Conole <aconole@redhat.com> Signed-off-by: Michael Santana <msantana@redhat.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: Luca Boccassi <bluca@debian.org> Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2019-03-25 15:32:08 +00:00
Public CI
M: Aaron Conole <aconole@redhat.com>
maintainers: update email address Change email address for Michael Santana to personal email in the MAINTAINERS file. Signed-off-by: Michael Santana <msantana@redhat.com> Signed-off-by: Michael Santana <maicolgabriel@hotmail.com> Acked-by: Aaron Conole <aconole@redhat.com>
2019-08-15 22:54:52 +00:00
M: Michael Santana <maicolgabriel@hotmail.com>
ci: introduce Travis builds for GitHub repositories GitHub is a service used by developers to store repositories. GitHub provides service integrations that allow 3rd party services to access developer repositories and perform actions. One of these services is Travis-CI, a simple continuous integration platform. This series introduces the ability for any github mirrors of the DPDK project, including developer mirrors, to kick off builds under the travis CI infrastructure. For now, this just means compilation - no other kinds of automated run exists yet. In the future, this can be expanded to execute and report results for any test-suites that might exist. This is a simple initial implementation of a travis build for the DPDK project. It doesn't require any changes from individual developers to enable, but will allow those developers who opt-in to GitHub and the travis service to get automatic builds for every push they make. The files added under .ci/ exist so that in the future, other CI support platforms (such as cirrus, appveyor, etc.) could have a common place to put their requisite scripts without polluting the main tree. Signed-off-by: Aaron Conole <aconole@redhat.com> Signed-off-by: Michael Santana <msantana@redhat.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: Luca Boccassi <bluca@debian.org> Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2019-03-25 15:32:08 +00:00
F: .travis.yml
F: .ci/
version: reference next ABI 21 for recent additions Change references to ABI 20.0.1 to use ABI v21, see https://doc.dpdk.org/guides/contributing/abi_policy.html#general-guidelines "Major ABI versions are declared no more frequently than yearly. Compatibility with the major ABI version is mandatory in subsequent releases until a new major ABI version is declared." Combined ABI policy and versioning in maintainers, add map files to the filter to more closely monitor future ABI changes. Signed-off-by: Ray Kinsella <mdr@ashroe.eu>
2020-04-30 10:27:26 +00:00
ABI Policy & Versioning
M: Ray Kinsella <mdr@ashroe.eu>
maintainers: add ABI versioning Reference the new framework and policy for ABI versioning, in the MAINTAINERS file. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-02-04 07:46:20 +00:00
M: Neil Horman <nhorman@tuxdriver.com>
eal: move common header files The EAL API (with doxygen documentation) is moved from common/include/ to include/, which makes more clear that it is the global API for all environments and architectures. Note that the arch-specific and OS-specific include files are not in this global include directory, but include/generic/ should cover the doxygen documentation for them. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: David Marchand <david.marchand@redhat.com>
2020-03-27 01:15:38 +00:00
F: lib/librte_eal/include/rte_compat.h
F: lib/librte_eal/include/rte_function_versioning.h
version: reference next ABI 21 for recent additions Change references to ABI 20.0.1 to use ABI v21, see https://doc.dpdk.org/guides/contributing/abi_policy.html#general-guidelines "Major ABI versions are declared no more frequently than yearly. Compatibility with the major ABI version is mandatory in subsequent releases until a new major ABI version is declared." Combined ABI policy and versioning in maintainers, add map files to the filter to more closely monitor future ABI changes. Signed-off-by: Ray Kinsella <mdr@ashroe.eu>
2020-04-30 10:27:26 +00:00
F: doc/guides/contributing/abi_*.rst
doc: rename ABI chapter to deprecation This chapter is for ABI and API. That's why a renaming is required. Remove also the examples which are now in the referenced guidelines. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-07-18 19:08:58 +00:00
F: doc/guides/rel_notes/deprecation.rst
devtools: add ABI checks For normal developers, those checks are disabled. Enabling them requires a configuration that will trigger the ABI dumps generation as part of the existing devtools/test-build.sh and devtools/test-meson-builds.sh scripts. Those checks are enabled in the CI for the default meson options on x86 and aarch64 so that proposed patches are validated via our CI robot. A cache of the ABI is stored in travis jobs to avoid rebuilding too often. Checks can be informational only, by setting ABI_CHECKS_WARN_ONLY when breaking the ABI in a future release. Explicit suppression rules have been added on internal structures exposed to crypto drivers as the current ABI policy does not apply to them. This could be improved in the future by carefully splitting the headers content with application and driver "users" in mind. We currently have issues reported for librte_crypto recent changes for which suppression rules have been added too. Mellanox glue libraries are explicitly skipped as they are not part of the application ABI. Signed-off-by: David Marchand <david.marchand@redhat.com> Acked-by: Luca Boccassi <bluca@debian.org>
2020-02-02 21:08:34 +00:00
F: devtools/check-abi.sh
devtools: move ABI scripts from buildtools Those scripts are only used by developers and not part of the build process. Move them to devtools so they are not installed. Signed-off-by: David Marchand <david.marchand@redhat.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2019-11-28 13:46:29 +00:00
F: devtools/check-abi-version.sh
devtools: add checks for ABI symbol addition Recently, some additional patches were added to allow for programmatic marking of C symbols as experimental. The addition of these markers is dependent on the manual addition of exported symbols to the EXPERIMENTAL section of the corresponding libraries version map file. The consensus on review is that, in addition to mandating the addition of symbols to the EXPERIMENTAL version in the map, we need a mechanism to enforce our documented process of mandating that addition when they are introduced. To that end, I am proposing this change. It is an addition to the checkpatches script, which scan incoming patches for additions and removals of symbols to the map file, and warns the user appropriately. Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
2018-06-27 18:01:01 +00:00
F: devtools/check-symbol-change.sh
devtools: add ABI checks For normal developers, those checks are disabled. Enabling them requires a configuration that will trigger the ABI dumps generation as part of the existing devtools/test-build.sh and devtools/test-meson-builds.sh scripts. Those checks are enabled in the CI for the default meson options on x86 and aarch64 so that proposed patches are validated via our CI robot. A cache of the ABI is stored in travis jobs to avoid rebuilding too often. Checks can be informational only, by setting ABI_CHECKS_WARN_ONLY when breaking the ABI in a future release. Explicit suppression rules have been added on internal structures exposed to crypto drivers as the current ABI policy does not apply to them. This could be improved in the future by carefully splitting the headers content with application and driver "users" in mind. We currently have issues reported for librte_crypto recent changes for which suppression rules have been added too. Mellanox glue libraries are explicitly skipped as they are not part of the application ABI. Signed-off-by: David Marchand <david.marchand@redhat.com> Acked-by: Luca Boccassi <bluca@debian.org>
2020-02-02 21:08:34 +00:00
F: devtools/gen-abi.sh
F: devtools/libabigail.abignore
devtools: move ABI scripts from buildtools Those scripts are only used by developers and not part of the build process. Move them to devtools so they are not installed. Signed-off-by: David Marchand <david.marchand@redhat.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2019-11-28 13:46:29 +00:00
F: devtools/update-abi.sh
F: devtools/update_version_map_abi.py
build: add internal tag check Add checks during build to ensure that all symbols in the INTERNAL version map section have __internal tags on their definitions, and enable the warnings needed to announce their use. Signed-off-by: Haiyue Wang <haiyue.wang@intel.com> Signed-off-by: David Marchand <david.marchand@redhat.com>
2020-04-25 10:56:17 +00:00
F: buildtools/check-symbols.sh
buildtools: detect discrepancies for experimental symbols When promoting those symbols as stable, there is no check to ensure that the final result is consistent. Add a little script to get the symbols per section from the library map files. Validate that all experimental symbols in object files are referenced by library map files. Signed-off-by: David Marchand <david.marchand@redhat.com> Acked-by: Adrien Mazarguil <adrien.mazarguil@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2019-06-29 11:58:48 +00:00
F: buildtools/map-list-symbol.sh
version: reference next ABI 21 for recent additions Change references to ABI 20.0.1 to use ABI v21, see https://doc.dpdk.org/guides/contributing/abi_policy.html#general-guidelines "Major ABI versions are declared no more frequently than yearly. Compatibility with the major ABI version is mandatory in subsequent releases until a new major ABI version is declared." Combined ABI policy and versioning in maintainers, add map files to the filter to more closely monitor future ABI changes. Signed-off-by: Ray Kinsella <mdr@ashroe.eu>
2020-04-30 10:27:26 +00:00
F: drivers/*/*/*.map
F: lib/*/*.map
scripts: add ABI checking utility There was a request for an abi validation utilty for the ongoing ABI stability work. As it turns out there is a abi compliance checker in development that seems to be under active development and provides fairly detailed ABI compliance reports. Its not yet intellegent enough to understand symbol versioning, but it does provide the ability to identify symbols which have changed between releases, along with details of the change, and offers developers the opportunity to identify which symbols then need versioning and validation for a given update via manual testing. This script automates the use of the compliance checker between two arbitrarily specified tags within the dpdk tree. To execute enter the $RTE_SDK directory and run: ./scripts/validate_abi.sh $GIT_TAG1 $GIT_TAG2 $CONFIG where $GIT_TAG1 and 2 are git tags and $CONFIG is a config specification suitable for passing as the T= variable in the make config command. Note the upstream source for the abi compliance checker is here: http://ispras.linuxbase.org/index.php/ABI_compliance_checker It generates a report for each DSO built from the requested tags that developers can review to find ABI compliance issues. Signed-off-by: Neil Horman <nhorman@tuxdriver.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-03-17 18:08:41 +00:00
maintainers: add section for pmdinfo The author of this feature is Neil Horman. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2016-07-07 09:59:33 +00:00
Driver information
maintainers: update for driver information tool I wrote pmdinfogen initially, and since there isn't a maintainer for it, I'll volunteer to take care of it Signed-off-by: Neil Horman <nhorman@tuxdriver.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2018-02-09 15:23:36 +00:00
M: Neil Horman <nhorman@tuxdriver.com>
maintainers: add section for pmdinfo The author of this feature is Neil Horman. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2016-07-07 09:59:33 +00:00
F: buildtools/pmdinfogen/
tools: move to usertools Rename tools/ into usertools/ to differentiate from buildtools/ and devtools/ while making clear these scripts are part of DPDK runtime. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Tested-by: Ferruh Yigit <ferruh.yigit@intel.com>
2016-12-15 21:25:36 +00:00
F: usertools/dpdk-pmdinfo.py
doc: add basic guide for pmdinfo This summarizes the "how to call dpdk-pmdinfo" in one place to be picked up by html/pdf/man-page docs. Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com> Acked-by: Luca Boccassi <lboccass@brocade.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-08-31 07:50:11 +00:00
F: doc/guides/tools/pmdinfo.rst
maintainers: add section for pmdinfo The author of this feature is Neil Horman. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2016-07-07 09:59:33 +00:00
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
Environment Abstraction Layer
-----------------------------
maintainers: set git tree for EAL and core libraries Without a git tree, the "guess" script from dpdk-ci will ignore all files that are referenced in those sections and let a patchset land in any subtree. Changes in the EAL, mbuf, mempool... go through the main repository. Signed-off-by: David Marchand <david.marchand@redhat.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2020-01-20 20:35:13 +00:00
T: git://dpdk.org/dpdk
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
EAL API and common code
eal: move arch-specific header files The arch-specific directories arm, ppc and x86 in common/include/arch/ are moved as include/ sub-directories of respective arch directories: - arm/include/ - ppc/include/ - x86/include/ Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Reviewed-by: Gavin Hu <gavin.hu@arm.com> Reviewed-by: David Christensen <drc@linux.vnet.ibm.com> Acked-by: David Marchand <david.marchand@redhat.com>
2020-03-27 01:15:36 +00:00
F: lib/librte_eal/common/
eal: introduce internal wrappers for file operations Introduce OS-independent wrappers in order to support common EAL code on Unix and Windows: * eal_file_open: open or create a file. * eal_file_lock: lock or unlock an open file. * eal_file_truncate: enforce a given size for an open file. Implementation for Linux and FreeBSD is placed in "unix" subdirectory, which is intended for common code between the two. These thin wrappers require no special maintenance. Common code supporting multi-process doesn't use the new wrappers, because it is inherently Unix-specific and would impose excessive requirements on the wrappers. Signed-off-by: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
2020-06-15 00:43:44 +00:00
F: lib/librte_eal/unix/
eal: move common header files The EAL API (with doxygen documentation) is moved from common/include/ to include/, which makes more clear that it is the global API for all environments and architectures. Note that the arch-specific and OS-specific include files are not in this global include directory, but include/generic/ should cover the doxygen documentation for them. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: David Marchand <david.marchand@redhat.com>
2020-03-27 01:15:38 +00:00
F: lib/librte_eal/include/
eal: use a single version map file Since the functions exported by DPDK EAL on all OS's should be identical, we should not need separate function version files for each OS. Therefore move existing version files to the top-level EAL directory. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2017-10-19 16:36:29 +00:00
F: lib/librte_eal/rte_eal_version.map
maintainers: dispatch more doc Documentation of build system, EAL and ring lib should be covered by the maintainers of the respective areas. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Olivier Matz <olivier.matz@6wind.com>
2015-02-04 08:08:45 +00:00
F: doc/guides/prog_guide/env_abstraction_layer.rst
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_alarm.c
F: app/test/test_atomic.c
F: app/test/test_barrier.c
F: app/test/test_byteorder.c
F: app/test/test_common.c
F: app/test/test_cpuflags.c
F: app/test/test_cycles.c
F: app/test/test_debug.c
F: app/test/test_eal*
F: app/test/test_errno.c
F: app/test/test_interrupts.c
F: app/test/test_logs.c
F: app/test/test_memcpy*
F: app/test/test_per_lcore.c
F: app/test/test_prefetch.c
F: app/test/test_reciprocal_division*
F: app/test/test_rwlock.c
F: app/test/test_spinlock.c
F: app/test/test_string_fns.c
F: app/test/test_tailq.c
F: app/test/test_version.c
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
trace: introduce new subsystem Define the public API for trace support. This patch also adds support for the build infrastructure and update the MAINTAINERS file for the trace subsystem. The 8 bytes tracepoint object is a global variable, and can be used in fast path. Created a new __rte_trace_point section to store the tracepoint objects as, - It is a mostly read-only data and not to mix with other "write" global variables. - Chances that the same subsystem fast path variables come in the same fast path cache line. i.e, it will enable a more predictable performance number from build to build. Signed-off-by: Jerin Jacob <jerinj@marvell.com> Signed-off-by: Sunil Kumar Kori <skori@marvell.com> Acked-by: David Marchand <david.marchand@redhat.com>
2020-04-22 19:03:19 +00:00
Trace - EXPERIMENTAL
M: Jerin Jacob <jerinj@marvell.com>
M: Sunil Kumar Kori <skori@marvell.com>
F: lib/librte_eal/include/rte_trace*.h
F: lib/librte_eal/common/eal_common_trace*.c
trace: implement register API The consumers of trace API defines the tracepoint and registers to eal. Internally these tracepoints will be stored in STAILQ for future use. This patch implements the tracepoint registration function. Signed-off-by: Jerin Jacob <jerinj@marvell.com> Acked-by: David Marchand <david.marchand@redhat.com>
2020-04-22 19:03:20 +00:00
F: lib/librte_eal/common/eal_trace.h
doc: add trace library guide Add programmer's guide for trace library support. Signed-off-by: Jerin Jacob <jerinj@marvell.com> Signed-off-by: Sunil Kumar Kori <skori@marvell.com> Acked-by: David Marchand <david.marchand@redhat.com>
2020-04-22 19:03:49 +00:00
F: doc/guides/prog_guide/trace_lib.rst
test/trace: add functional test cases Example commands to run UT and check the traces with babeltrace viewer. - Delete the existing /root/dpdk-traces/ directory if needed. > sudo rm -rf /root/dpdk-traces/ - Start the dpdk-test > sudo ./build/app/test/dpdk-test -c 0x3 - --trace=.* - Run trace_autotest > trace_autotest - View the traces with babletrace viewer. > sudo babeltrace /root/dpdk-traces/ Signed-off-by: Sunil Kumar Kori <skori@marvell.com> Acked-by: David Marchand <david.marchand@redhat.com>
2020-04-22 19:03:43 +00:00
F: app/test/test_trace*
trace: introduce new subsystem Define the public API for trace support. This patch also adds support for the build infrastructure and update the MAINTAINERS file for the trace subsystem. The 8 bytes tracepoint object is a global variable, and can be used in fast path. Created a new __rte_trace_point section to store the tracepoint objects as, - It is a mostly read-only data and not to mix with other "write" global variables. - Chances that the same subsystem fast path variables come in the same fast path cache line. i.e, it will enable a more predictable performance number from build to build. Signed-off-by: Jerin Jacob <jerinj@marvell.com> Signed-off-by: Sunil Kumar Kori <skori@marvell.com> Acked-by: David Marchand <david.marchand@redhat.com>
2020-04-22 19:03:19 +00:00
mem: move librte_malloc to eal/common Move malloc inside eal and create a new section in MAINTAINERS file for Memory Allocation in EAL. Create a dummy malloc library to avoid breaking applications that have librte_malloc in their DT_NEEDED entries. This is the first step towards using malloc to allocate memory directly from memsegs. Thus, memzones would allocate memory through malloc, allowing to free memzones. Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-07-15 16:32:20 +00:00
Memory Allocation
maintainers: resign from maintenance I will not be directly working on the DPDK project anymore. Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2017-12-18 14:02:06 +00:00
M: Anatoly Burakov <anatoly.burakov@intel.com>
eal: move common header files The EAL API (with doxygen documentation) is moved from common/include/ to include/, which makes more clear that it is the global API for all environments and architectures. Note that the arch-specific and OS-specific include files are not in this global include directory, but include/generic/ should cover the doxygen documentation for them. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: David Marchand <david.marchand@redhat.com>
2020-03-27 01:15:38 +00:00
F: lib/librte_eal/include/rte_fbarray.h
F: lib/librte_eal/include/rte_mem*
F: lib/librte_eal/include/rte_malloc.h
mem: move librte_malloc to eal/common Move malloc inside eal and create a new section in MAINTAINERS file for Memory Allocation in EAL. Create a dummy malloc library to avoid breaking applications that have librte_malloc in their DT_NEEDED entries. This is the first step towards using malloc to allocate memory directly from memsegs. Thus, memzones would allocate memory through malloc, allowing to free memzones. Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-07-15 16:32:20 +00:00
F: lib/librte_eal/common/*malloc*
mem: extract common dynamic memory allocation Code in Linux EAL that supports dynamic memory allocation (as opposed to static allocation used by FreeBSD) is not OS-dependent and can be reused by Windows EAL. Move such code to a file compiled only for the OS that require it. Keep Anatoly Burakov maintainer of extracted code. Signed-off-by: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
2020-06-15 00:43:47 +00:00
F: lib/librte_eal/common/eal_common_dynmem.c
maintainers: claim EAL memory init Claim maintainership of all areas of EAL memory init, including OS-specific parts of it. Also, claim maintainership of fbarray, since although it's not related to memory allocation, it is heavily used by it and its primary purpose is to serve memory allocation functions, and thus will appear under "memory allocation" banner. Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2018-04-23 12:29:57 +00:00
F: lib/librte_eal/common/eal_common_fbarray.c
mem: move librte_malloc to eal/common Move malloc inside eal and create a new section in MAINTAINERS file for Memory Allocation in EAL. Create a dummy malloc library to avoid breaking applications that have librte_malloc in their DT_NEEDED entries. This is the first step towards using malloc to allocate memory directly from memsegs. Thus, memzones would allocate memory through malloc, allowing to free memzones. Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-07-15 16:32:20 +00:00
F: lib/librte_eal/common/eal_common_mem*
F: lib/librte_eal/common/eal_hugepages.h
eal: move OS-specific sub-directories Since the kernel modules are moved to kernel/ directory, there is no need anymore for the sub-directory eal/ in linux/, freebsd/ and windows/. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: David Marchand <david.marchand@redhat.com>
2020-03-27 01:15:39 +00:00
F: lib/librte_eal/linux/eal_mem*
F: lib/librte_eal/freebsd/eal_mem*
doc: update malloc guide Update malloc documentation to reflect new implementation details. Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-07-16 07:37:11 +00:00
F: doc/guides/prog_guide/env_abstraction_layer.rst
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_external_mem.c
F: app/test/test_func_reentrancy.c
F: app/test/test_fbarray.c
F: app/test/test_malloc.c
F: app/test/test_memory.c
F: app/test/test_memzone.c
mem: move librte_malloc to eal/common Move malloc inside eal and create a new section in MAINTAINERS file for Memory Allocation in EAL. Create a dummy malloc library to avoid breaking applications that have librte_malloc in their DT_NEEDED entries. This is the first step towards using malloc to allocate memory directly from memsegs. Thus, memzones would allocate memory through malloc, allowing to free memzones. Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-07-15 16:32:20 +00:00
eal: add keep alive monitoring Adds functions for detecting and reporting the live-ness of LCores, the primary requirement of which is minimal overheads for the core(s) being checked. Core failures are notified via an application defined callback. Signed-off-by: Remy Horton <remy.horton@intel.com>
2015-11-18 14:05:14 +00:00
Keep alive
eal: move common header files The EAL API (with doxygen documentation) is moved from common/include/ to include/, which makes more clear that it is the global API for all environments and architectures. Note that the arch-specific and OS-specific include files are not in this global include directory, but include/generic/ should cover the doxygen documentation for them. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: David Marchand <david.marchand@redhat.com>
2020-03-27 01:15:38 +00:00
F: lib/librte_eal/include/rte_keepalive.h
eal: add keep alive monitoring Adds functions for detecting and reporting the live-ness of LCores, the primary requirement of which is minimal overheads for the core(s) being checked. Core failures are notified via an application defined callback. Signed-off-by: Remy Horton <remy.horton@intel.com>
2015-11-18 14:05:14 +00:00
F: lib/librte_eal/common/rte_keepalive.c
examples/l2fwd-keepalive: add sample application Modified version of l2fwd to demonstrate keep-alive functionality. Signed-off-by: Remy Horton <remy.horton@intel.com> Signed-off-by: Maryam Tahhan <maryam.tahhan@intel.com> Signed-off-by: John J Browne <john.j.browne@intel.com>
2015-11-18 14:05:16 +00:00
F: examples/l2fwd-keepalive/
F: doc/guides/sample_app_ug/keep_alive.rst
eal: add keep alive monitoring Adds functions for detecting and reporting the live-ness of LCores, the primary requirement of which is minimal overheads for the core(s) being checked. Core failures are notified via an application defined callback. Signed-off-by: Remy Horton <remy.horton@intel.com>
2015-11-18 14:05:14 +00:00
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
Secondary process
maintainers: resign from maintenance I will not be directly working on the DPDK project anymore. Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2017-12-18 14:02:06 +00:00
M: Anatoly Burakov <anatoly.burakov@intel.com>
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
K: RTE_PROC_
maintainers: claim maintainership of IPC IPC is a big part of secondary process infrastructure now, and I have been de-facto maintainer for it since 18.05. Update MAINTAINERS file to match. Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
2019-04-25 13:17:51 +00:00
F: lib/librte_eal/common/eal_common_proc.c
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: doc/guides/prog_guide/multi_proc_support.rst
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_mp_secondary.c
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: examples/multi_process/
F: doc/guides/sample_app_ug/multi_process.rst
service: remove experimental tags This commit removes the experimental tags from the service cores functions, they now become part of the main DPDK API/ABI. Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2018-04-05 13:15:46 +00:00
Service Cores
service: introduce service cores concept Add header files, update .map files with new service functions, and add the service header to the doxygen for building. This service header API allows DPDK to use services as a concept of something that requires CPU cycles. An example is a PMD that runs in software to schedule events, where a hardware version exists that does not require a CPU. Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2017-07-11 14:19:27 +00:00
M: Harry van Haaren <harry.van.haaren@intel.com>
eal: move common header files The EAL API (with doxygen documentation) is moved from common/include/ to include/, which makes more clear that it is the global API for all environments and architectures. Note that the arch-specific and OS-specific include files are not in this global include directory, but include/generic/ should cover the doxygen documentation for them. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: David Marchand <david.marchand@redhat.com>
2020-03-27 01:15:38 +00:00
F: lib/librte_eal/include/rte_service.h
F: lib/librte_eal/include/rte_service_component.h
service: introduce service cores concept Add header files, update .map files with new service functions, and add the service header to the doxygen for building. This service header API allows DPDK to use services as a concept of something that requires CPU cycles. An example is a PMD that runs in software to schedule events, where a hardware version exists that does not require a CPU. Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2017-07-11 14:19:27 +00:00
F: lib/librte_eal/common/rte_service.c
F: doc/guides/prog_guide/service_cores.rst
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_service_cores.c
service: introduce service cores concept Add header files, update .map files with new service functions, and add the service header to the doxygen for building. This service header API allows DPDK to use services as a concept of something that requires CPU cycles. An example is a PMD that runs in software to schedule events, where a hardware version exists that does not require a CPU. Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2017-07-11 14:19:27 +00:00
eal: move bitmap from sched library The librte_sched uses rte_bitmap to manage large arrays of bits in an optimized method so, moving it to eal/common would allow other libraries and applications to use it. Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2017-09-21 11:50:20 +00:00
Bitmap
M: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
eal: move common header files The EAL API (with doxygen documentation) is moved from common/include/ to include/, which makes more clear that it is the global API for all environments and architectures. Note that the arch-specific and OS-specific include files are not in this global include directory, but include/generic/ should cover the doxygen documentation for them. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: David Marchand <david.marchand@redhat.com>
2020-03-27 01:15:38 +00:00
F: lib/librte_eal/include/rte_bitmap.h
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_bitmap.c
eal: move bitmap from sched library The librte_sched uses rte_bitmap to manage large arrays of bits in an optimized method so, moving it to eal/common would allow other libraries and applications to use it. Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2017-09-21 11:50:20 +00:00
mcslock: add MCS queued lock implementation If there are multiple threads contending, they all attempt to take the spinlock lock at the same time once it is released. This results in a huge amount of processor bus traffic, which is a huge performance killer. Thus, if we somehow order the lock-takers so that they know who is next in line for the resource we can vastly reduce the amount of bus traffic. This patch added MCS lock library. It provides scalability by spinning on a CPU/thread local variable which avoids expensive cache bouncings. It provides fairness by maintaining a list of acquirers and passing the lock to each CPU/thread in the order they acquired the lock. Signed-off-by: Phil Yang <phil.yang@arm.com> Reviewed-by: Steve Capper <steve.capper@arm.com> Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com> Reviewed-by: Gavin Hu <gavin.hu@arm.com>
2019-07-05 10:27:06 +00:00
MCSlock - EXPERIMENTAL
M: Phil Yang <phil.yang@arm.com>
eal: move common header files The EAL API (with doxygen documentation) is moved from common/include/ to include/, which makes more clear that it is the global API for all environments and architectures. Note that the arch-specific and OS-specific include files are not in this global include directory, but include/generic/ should cover the doxygen documentation for them. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: David Marchand <david.marchand@redhat.com>
2020-03-27 01:15:38 +00:00
F: lib/librte_eal/include/generic/rte_mcslock.h
test/mcslock: add MCS queued lock unit test Unit test and perf test for MCS queued lock. Signed-off-by: Phil Yang <phil.yang@arm.com> Reviewed-by: Gavin Hu <gavin.hu@arm.com> Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
2019-07-05 10:27:08 +00:00
F: app/test/test_mcslock.c
mcslock: add MCS queued lock implementation If there are multiple threads contending, they all attempt to take the spinlock lock at the same time once it is released. This results in a huge amount of processor bus traffic, which is a huge performance killer. Thus, if we somehow order the lock-takers so that they know who is next in line for the resource we can vastly reduce the amount of bus traffic. This patch added MCS lock library. It provides scalability by spinning on a CPU/thread local variable which avoids expensive cache bouncings. It provides fairness by maintaining a list of acquirers and passing the lock to each CPU/thread in the order they acquired the lock. Signed-off-by: Phil Yang <phil.yang@arm.com> Reviewed-by: Steve Capper <steve.capper@arm.com> Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com> Reviewed-by: Gavin Hu <gavin.hu@arm.com>
2019-07-05 10:27:06 +00:00
ticketlock: introduce fair ticket based locking The spinlock implementation is unfair, some threads may take locks aggressively while leaving the other threads starving for long time. This patch introduces ticketlock which gives each waiting thread a ticket and they can take the lock one by one. First come, first serviced. This avoids starvation for too long time and is more predictable. Suggested-by: Jerin Jacob <jerinj@marvell.com> Signed-off-by: Joyce Kong <joyce.kong@arm.com> Reviewed-by: Gavin Hu <gavin.hu@arm.com> Reviewed-by: Ola Liljedahl <ola.liljedahl@arm.com> Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
2019-03-25 11:11:07 +00:00
Ticketlock
M: Joyce Kong <joyce.kong@arm.com>
eal: move common header files The EAL API (with doxygen documentation) is moved from common/include/ to include/, which makes more clear that it is the global API for all environments and architectures. Note that the arch-specific and OS-specific include files are not in this global include directory, but include/generic/ should cover the doxygen documentation for them. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: David Marchand <david.marchand@redhat.com>
2020-03-27 01:15:38 +00:00
F: lib/librte_eal/include/generic/rte_ticketlock.h
test/ticketlock: add test cases Add test cases for ticket lock, recursive ticket lock, and ticket lock performance. Signed-off-by: Joyce Kong <joyce.kong@arm.com> Reviewed-by: Gavin Hu <gavin.hu@arm.com> Reviewed-by: Phil Yang <phil.yang@arm.com> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
2019-03-25 11:11:09 +00:00
F: app/test/test_ticketlock.c
ticketlock: introduce fair ticket based locking The spinlock implementation is unfair, some threads may take locks aggressively while leaving the other threads starving for long time. This patch introduces ticketlock which gives each waiting thread a ticket and they can take the lock one by one. First come, first serviced. This avoids starvation for too long time and is more predictable. Suggested-by: Jerin Jacob <jerinj@marvell.com> Signed-off-by: Joyce Kong <joyce.kong@arm.com> Reviewed-by: Gavin Hu <gavin.hu@arm.com> Reviewed-by: Ola Liljedahl <ola.liljedahl@arm.com> Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
2019-03-25 11:11:07 +00:00
eal: replace libc-based random generation with LFSR This commit replaces rte_rand()'s use of lrand48() with a DPDK-native combined Linear Feedback Shift Register (LFSR) (also known as Tausworthe) pseudo-random number generator. This generator is faster and produces better-quality random numbers than the linear congruential generator (LCG) of lib's lrand48(). The implementation, as opposed to lrand48(), is multi-thread safe in regards to concurrent rte_rand() calls from different lcore threads. A LCG is still used, but only to seed the five per-lcore LFSR sequences. In addition, this patch also addresses the issue of the legacy implementation only producing 62 bits of pseudo randomness, while the API requires all 64 bits to be random. This pseudo-random number generator is not cryptographically secure - just like lrand48(). Bugzilla ID: 114 Bugzilla ID: 276 Signed-off-by: Mattias Rönnblom <mattias.ronnblom@ericsson.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2019-06-28 09:01:20 +00:00
Pseudo-random Number Generation
M: Mattias Rönnblom <mattias.ronnblom@ericsson.com>
eal: move common header files The EAL API (with doxygen documentation) is moved from common/include/ to include/, which makes more clear that it is the global API for all environments and architectures. Note that the arch-specific and OS-specific include files are not in this global include directory, but include/generic/ should cover the doxygen documentation for them. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: David Marchand <david.marchand@redhat.com>
2020-03-27 01:15:38 +00:00
F: lib/librte_eal/include/rte_random.h
eal: replace libc-based random generation with LFSR This commit replaces rte_rand()'s use of lrand48() with a DPDK-native combined Linear Feedback Shift Register (LFSR) (also known as Tausworthe) pseudo-random number generator. This generator is faster and produces better-quality random numbers than the linear congruential generator (LCG) of lib's lrand48(). The implementation, as opposed to lrand48(), is multi-thread safe in regards to concurrent rte_rand() calls from different lcore threads. A LCG is still used, but only to seed the five per-lcore LFSR sequences. In addition, this patch also addresses the issue of the legacy implementation only producing 62 bits of pseudo randomness, while the API requires all 64 bits to be random. This pseudo-random number generator is not cryptographically secure - just like lrand48(). Bugzilla ID: 114 Bugzilla ID: 276 Signed-off-by: Mattias Rönnblom <mattias.ronnblom@ericsson.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2019-06-28 09:01:20 +00:00
F: lib/librte_eal/common/rte_random.c
F: app/test/test_rand_perf.c
mk: introduce ARMv7 architecture Make DPDK run on ARMv7-A architecture. This patch assumes ARM Cortex-A9. However, it is known to be working on Cortex-A7 and Cortex-A15. Signed-off-by: Vlastimil Kosar <kosar@rehivetech.com> Signed-off-by: Jan Viktorin <viktorin@rehivetech.com> Acked-by: David Marchand <david.marchand@6wind.com>
2015-11-02 23:47:27 +00:00
ARM v7
M: Jan Viktorin <viktorin@rehivetech.com>
maintainers: update for Arm v7 and v8 Updating ARM v7 and v8 maintainer. Gavin is leaving Arm. Signed-off-by: Ruifeng Wang <ruifeng.wang@arm.com> Acked-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
2020-04-27 07:57:56 +00:00
M: Ruifeng Wang <ruifeng.wang@arm.com>
eal: move arch-specific C files The arch-specific directories arm, ppc and x86 in common/arch/ are moved at the same level as the OS-specific directories. It makes more clear that EAL is covering a matrix combining OS and arch. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Reviewed-by: David Christensen <drc@linux.vnet.ibm.com> Acked-by: David Marchand <david.marchand@redhat.com>
2020-03-27 01:15:35 +00:00
F: lib/librte_eal/arm/
mk: introduce ARMv7 architecture Make DPDK run on ARMv7-A architecture. This patch assumes ARM Cortex-A9. However, it is known to be working on Cortex-A7 and Cortex-A15. Signed-off-by: Vlastimil Kosar <kosar@rehivetech.com> Signed-off-by: Jan Viktorin <viktorin@rehivetech.com> Acked-by: David Marchand <david.marchand@6wind.com>
2015-11-02 23:47:27 +00:00
mk: introduce ARMv8 architecture Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2015-11-06 09:40:28 +00:00
ARM v8
maintainers: update Cavium email ids Following Marvell's acquisition of Cavium, we need to update all the Cavium maintainer's entries to point to our new e-mail addresses. Update maintainers as they are no longer working for Cavium. Thanks to Harish Patil for his support and development of our various dpdk drivers. Signed-off-by: Jerin Jacob <jerinj@marvell.com>
2018-12-16 15:43:25 +00:00
M: Jerin Jacob <jerinj@marvell.com>
maintainers: update for Arm v7 and v8 Updating ARM v7 and v8 maintainer. Gavin is leaving Arm. Signed-off-by: Ruifeng Wang <ruifeng.wang@arm.com> Acked-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
2020-04-27 07:57:56 +00:00
M: Ruifeng Wang <ruifeng.wang@arm.com>
eal: move arch-specific header files The arch-specific directories arm, ppc and x86 in common/include/arch/ are moved as include/ sub-directories of respective arch directories: - arm/include/ - ppc/include/ - x86/include/ Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Reviewed-by: Gavin Hu <gavin.hu@arm.com> Reviewed-by: David Christensen <drc@linux.vnet.ibm.com> Acked-by: David Marchand <david.marchand@redhat.com>
2020-03-27 01:15:36 +00:00
F: lib/librte_eal/arm/include/*_64.h
net: implement CRC for ARM64 NEON Added CRC compute APIs for arm64 utilizing the pmull capability. Added new file net_crc_neon.h to hold the arm64 pmull CRC implementation. Added wrappers in rte_vect.h for those neon intrinsics which are not supported in GCC version < 7. Verified the changes with crc_autotest unit test case Signed-off-by: Ashwin Sekhar T K <ashwin.sekhar@caviumnetworks.com> Acked-by: Jianbo Liu <jianbo.liu@linaro.org>
2017-07-04 09:24:07 +00:00
F: lib/librte_net/net_crc_neon.h
mk: introduce ARMv8 architecture Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2015-11-06 09:40:28 +00:00
F: lib/librte_acl/acl_run_neon.*
bpf/arm: add build infrastructure Add build infrastructure and documentation update for arm64 JIT support. Signed-off-by: Jerin Jacob <jerinj@marvell.com> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
2019-09-03 10:59:31 +00:00
F: lib/librte_bpf/bpf_jit_arm64.c
lpm/arm: support NEON Enabled CONFIG_RTE_LIBRTE_LPM, CONFIG_RTE_LIBRTE_TABLE, CONFIG_RTE_LIBRTE_PIPELINE libraries for arm and arm64 TABLE, PIPELINE libraries were disabled due to LPM library dependency. Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Signed-off-by: Jianbo Liu <jianbo.liu@linaro.org>
2016-03-11 03:52:58 +00:00
F: lib/librte_lpm/rte_lpm_neon.h
maintainers: claim responsibility for arm64 files of hash Fixes: f123e3d2ca92 ("hash: replace libc memcmp with optimized functions for arm64") Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2016-03-11 03:52:59 +00:00
F: lib/librte_hash/rte*_arm64.h
efd: support lookup using NEON intrinsics * Added file lib/librte_efd/rte_efd_arm64.h to hold arm64 specific definitions * Verified the changes with efd_autotest unit test case Signed-off-by: Ashwin Sekhar T K <ashwin.sekhar@caviumnetworks.com>
2017-04-27 12:44:18 +00:00
F: lib/librte_efd/rte*_arm64.h
table: add NEON implementation of LRU strategy 3 * Added new file rte_lru_arm64.h for holding arm64 specific definitions * Verified the changes with table_autotest unit test case Signed-off-by: Ashwin Sekhar T K <ashwin.sekhar@caviumnetworks.com>
2017-04-28 08:58:31 +00:00
F: lib/librte_table/rte*_arm64.h
net/ixgbe: implement vector driver for ARM Use ARM NEON intrinsic to implement ixgbe vPMD Signed-off-by: Jianbo Liu <jianbo.liu@linaro.org> Acked-by: Bruce Richardson <bruce.richardson@intel.com> [style fixes as highlighted by checkpatch.pl] Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2016-05-06 06:25:46 +00:00
F: drivers/net/ixgbe/ixgbe_rxtx_vec_neon.c
net/i40e: implement vector PMD for ARM Use ARM NEON intrinsic to implement i40e vPMD Signed-off-by: Jianbo Liu <jianbo.liu@linaro.org> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2016-10-14 04:00:01 +00:00
F: drivers/net/i40e/i40e_rxtx_vec_neon.c
net/virtio: add NEON based Rx handler Added neon based Rx vector implementation. Selection of the new handler based neon availability at runtime. Updated the release notes and MAINTAINERS file. Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Acked-by: Yuanhan Liu <yuanhan.liu@linux.intel.com> Acked-by: Jianbo Liu <jianbo.liu@linaro.org>
2016-08-18 04:12:11 +00:00
F: drivers/net/virtio/virtio_rxtx_simple_neon.c
mk: introduce ARMv8 architecture Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2015-11-06 09:40:28 +00:00
mem: fix anonymous mapping on Power9 Removed the use of MAP_HUGETLB for anonymous mapping on ppc64. The MAP_HUGETLB had previously been added to workaround issues on IBM Power8 systems when mapping /dev/zero. In the current code the MAP_HUGETLB flag will cause the anonymous mapping to fail on Power9. Note, Power8 is currently failing to correctly mmap Hugepages, with and without this change. Fixes: 284ae3e9ff9a ("eal/ppc: fix mmap for memory initialization") Signed-off-by: David Wilder <dwilder@us.ibm.com> Reviewed-by: Pradeep Satyanarayana <pradeep@us.ibm.com>
2018-11-16 17:35:38 +00:00
IBM POWER (alpha)
maintainers: update for IBM POWER Succeed Chao Zhu as maintainer of EAL for IBM POWER. Cc: stable@dpdk.org Signed-off-by: David Christensen <drc@linux.vnet.ibm.com> Acked-by: Chao Zhu <chaozhu@linux.vnet.ibm.com>
2019-03-27 22:31:39 +00:00
M: David Christensen <drc@linux.vnet.ibm.com>
eal: move arch-specific C files The arch-specific directories arm, ppc and x86 in common/arch/ are moved at the same level as the OS-specific directories. It makes more clear that EAL is covering a matrix combining OS and arch. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Reviewed-by: David Christensen <drc@linux.vnet.ibm.com> Acked-by: David Marchand <david.marchand@redhat.com>
2020-03-27 01:15:35 +00:00
F: lib/librte_eal/ppc/
net/i40e: implement vector PMD for altivec This patch enables i40e driver in PowerPC along with its altivec intrinsic support. Signed-off-by: Gowrishankar Muthukrishnan <gowrishankar.m@linux.vnet.ibm.com> Acked-by: Chao Zhu <chaozhu@linux.vnet.ibm.com>
2017-02-23 04:39:08 +00:00
F: drivers/net/i40e/i40e_rxtx_vec_altivec.c
examples/l3fwd: optimize packet processing on powerpc This patch adds altivec support for lpm packet processing in powerpc. Signed-off-by: Gowrishankar Muthukrishnan <gowrishankar.m@linux.vnet.ibm.com> Acked-by: Chao Zhu <chaozhu@linux.vnet.ibm.com>
2017-09-21 10:05:24 +00:00
F: examples/l3fwd/*altivec.h
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
Intel x86
maintainers: claim EAL Intel x86 Signed-off-by: Konstantin Ananyev <konstantin.ananyev@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-03-11 11:14:30 +00:00
M: Bruce Richardson <bruce.richardson@intel.com>
M: Konstantin Ananyev <konstantin.ananyev@intel.com>
eal: move arch-specific C files The arch-specific directories arm, ppc and x86 in common/arch/ are moved at the same level as the OS-specific directories. It makes more clear that EAL is covering a matrix combining OS and arch. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Reviewed-by: David Christensen <drc@linux.vnet.ibm.com> Acked-by: David Marchand <david.marchand@redhat.com>
2020-03-27 01:15:35 +00:00
F: lib/librte_eal/x86/
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
Linux EAL (with overlaps)
eal: move OS-specific sub-directories Since the kernel modules are moved to kernel/ directory, there is no need anymore for the sub-directory eal/ in linux/, freebsd/ and windows/. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: David Marchand <david.marchand@redhat.com>
2020-03-27 01:15:39 +00:00
F: lib/librte_eal/linux/
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: doc/guides/linux_gsg/
Linux UIO
maintainers: claim responsibility for igb_uio igb_iuo has no maintainer, claim responsibility for igb_uio Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Helin Zhang <helin.zhang@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2016-03-04 15:07:11 +00:00
M: Ferruh Yigit <ferruh.yigit@intel.com>
move kernel modules directories This patch moves the kernel modules code from EAL to a common place. - Separate the kernel module code from user space code. Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com> Tested-by: Bruce Richardson <bruce.richardson@intel.com>
2018-02-22 06:09:05 +00:00
F: kernel/linux/igb_uio/
pci: introduce library and driver The PCI lib defines the types and methods allowing to use PCI elements. The PCI bus implements a bus driver for PCI devices by constructing rte_bus elements using the PCI lib. Move the relevant code out of the EAL to its expected place. Libraries, drivers, unit tests and applications are updated to use the new rte_bus_pci.h header when necessary. Signed-off-by: Gaetan Rivet <gaetan.rivet@6wind.com>
2017-10-26 10:06:08 +00:00
F: drivers/bus/pci/linux/*uio*
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
Linux VFIO
maintainers: claim VFIO and IVSHMEM Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-02-24 11:19:18 +00:00
M: Anatoly Burakov <anatoly.burakov@intel.com>
eal: move OS-specific sub-directories Since the kernel modules are moved to kernel/ directory, there is no need anymore for the sub-directory eal/ in linux/, freebsd/ and windows/. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: David Marchand <david.marchand@redhat.com>
2020-03-27 01:15:39 +00:00
F: lib/librte_eal/linux/*vfio*
pci: introduce library and driver The PCI lib defines the types and methods allowing to use PCI elements. The PCI bus implements a bus driver for PCI devices by constructing rte_bus elements using the PCI lib. Move the relevant code out of the EAL to its expected place. Libraries, drivers, unit tests and applications are updated to use the new rte_bus_pci.h header when necessary. Signed-off-by: Gaetan Rivet <gaetan.rivet@6wind.com>
2017-10-26 10:06:08 +00:00
F: drivers/bus/pci/linux/*vfio*
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
FreeBSD EAL (with overlaps)
maintainers: claim FreeBSD eal and distributor Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-02-06 13:55:35 +00:00
M: Bruce Richardson <bruce.richardson@intel.com>
eal: move OS-specific sub-directories Since the kernel modules are moved to kernel/ directory, there is no need anymore for the sub-directory eal/ in linux/, freebsd/ and windows/. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: David Marchand <david.marchand@redhat.com>
2020-03-27 01:15:39 +00:00
F: lib/librte_eal/freebsd/
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: doc/guides/freebsd_gsg/
FreeBSD contigmem
maintainers: claim FreeBSD eal and distributor Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-02-06 13:55:35 +00:00
M: Bruce Richardson <bruce.richardson@intel.com>
move kernel modules directories This patch moves the kernel modules code from EAL to a common place. - Separate the kernel module code from user space code. Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com> Tested-by: Bruce Richardson <bruce.richardson@intel.com>
2018-02-22 06:09:05 +00:00
F: kernel/freebsd/contigmem/
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
FreeBSD UIO
maintainers: claim FreeBSD eal and distributor Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-02-06 13:55:35 +00:00
M: Bruce Richardson <bruce.richardson@intel.com>
move kernel modules directories This patch moves the kernel modules code from EAL to a common place. - Separate the kernel module code from user space code. Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com> Tested-by: Bruce Richardson <bruce.richardson@intel.com>
2018-02-22 06:09:05 +00:00
F: kernel/freebsd/nic_uio/
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
eal/windows: introduce Windows support Added initial stub source files and required meson changes for Windows support. kernel/windows/meson is a stub file added to support Windows specific source in future releases. Signed-off-by: Pallavi Kadam <pallavi.kadam@intel.com> Signed-off-by: Anand Rawat <anand.rawat@intel.com> Reviewed-by: Jeff Shaw <jeffrey.b.shaw@intel.com> Reviewed-by: Ranjit Menon <ranjit.menon@intel.com> Acked-by: Harini Ramakrishnan <harini.ramakrishnan@microsoft.com>
2019-04-02 03:54:49 +00:00
Windows support
M: Harini Ramakrishnan <harini.ramakrishnan@microsoft.com>
M: Omar Cardona <ocardona@microsoft.com>
maintainers: update for Windows Since Anand is no longer with Intel, Pallavi will replace him as maintainer. Signed-off-by: Ranjit Menon <ranjit.menon@intel.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2020-01-13 19:35:34 +00:00
M: Pallavi Kadam <pallavi.kadam@intel.com>
eal/windows: introduce Windows support Added initial stub source files and required meson changes for Windows support. kernel/windows/meson is a stub file added to support Windows specific source in future releases. Signed-off-by: Pallavi Kadam <pallavi.kadam@intel.com> Signed-off-by: Anand Rawat <anand.rawat@intel.com> Reviewed-by: Jeff Shaw <jeffrey.b.shaw@intel.com> Reviewed-by: Ranjit Menon <ranjit.menon@intel.com> Acked-by: Harini Ramakrishnan <harini.ramakrishnan@microsoft.com>
2019-04-02 03:54:49 +00:00
M: Ranjit Menon <ranjit.menon@intel.com>
F: lib/librte_eal/windows/
build: add module definition files for Windows Updated lib/meson.build to create shared libraries on Windows. Added DEF files to list the exports for the eal and kvargs libraries. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Signed-off-by: Anand Rawat <anand.rawat@intel.com> Reviewed-by: Pallavi Kadam <pallavi.kadam@intel.com> Reviewed-by: Ranjit Menon <ranjit.menon@intel.com> Acked-by: Harini Ramakrishnan <harini.ramakrishnan@microsoft.com>
2019-04-02 03:54:53 +00:00
F: lib/librte_eal/rte_eal_exports.def
doc: add guide for Windows Added documentation to build helloworld example on Windows using meson and clang. Signed-off-by: Pallavi Kadam <pallavi.kadam@intel.com> Signed-off-by: Anand Rawat <anand.rawat@intel.com> Reviewed-by: Jeff Shaw <jeffrey.b.shaw@intel.com> Reviewed-by: Ranjit Menon <ranjit.menon@intel.com> Tested-by: Harini Ramakrishnan <harini.ramakrishnan@microsoft.com> Acked-by: Harini Ramakrishnan <harini.ramakrishnan@microsoft.com>
2019-04-02 03:54:57 +00:00
F: doc/guides/windows_gsg/
eal/windows: introduce Windows support Added initial stub source files and required meson changes for Windows support. kernel/windows/meson is a stub file added to support Windows specific source in future releases. Signed-off-by: Pallavi Kadam <pallavi.kadam@intel.com> Signed-off-by: Anand Rawat <anand.rawat@intel.com> Reviewed-by: Jeff Shaw <jeffrey.b.shaw@intel.com> Reviewed-by: Ranjit Menon <ranjit.menon@intel.com> Acked-by: Harini Ramakrishnan <harini.ramakrishnan@microsoft.com>
2019-04-02 03:54:49 +00:00
eal/windows: initialize hugepage info Add hugepages discovery ("large pages" in Windows terminology) and update documentation for required privilege setup. Only 2MB hugepages are supported and their number is estimated roughly due to the lack or unstable status of suitable OS APIs. Assign myself as maintainer for the implementation file. Signed-off-by: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
2020-06-15 00:43:53 +00:00
Windows memory allocation
M: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
F: lib/librte_eal/windows/eal_hugepages.c
eal/windows: implement basic memory management Basic memory management supports core libraries and PMDs operating in IOVA as PA mode. It uses a kernel-mode driver, virt2phys, to obtain IOVAs of hugepages allocated from user-mode. Multi-process mode is not implemented and is forcefully disabled at startup. Assign myself as a maintainer for Windows file and memory management implementation. Signed-off-by: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
2020-06-15 00:43:54 +00:00
F: lib/librte_eal/windows/eal_mem*
eal/windows: initialize hugepage info Add hugepages discovery ("large pages" in Windows terminology) and update documentation for required privilege setup. Only 2MB hugepages are supported and their number is estimated roughly due to the lack or unstable status of suitable OS APIs. Assign myself as maintainer for the implementation file. Signed-off-by: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
2020-06-15 00:43:53 +00:00
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
Core Libraries
--------------
maintainers: set git tree for EAL and core libraries Without a git tree, the "guess" script from dpdk-ci will ignore all files that are referenced in those sections and let a patchset land in any subtree. Changes in the EAL, mbuf, mempool... go through the main repository. Signed-off-by: David Marchand <david.marchand@redhat.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2020-01-20 20:35:13 +00:00
T: git://dpdk.org/dpdk
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
maintainers: claim mbuf, mempool, ring, mk, kvargs, cmdline I'm volunteer to maintain the following components of dpdk: - mbuf packet api - mempool library - ring library - build system - kvargs - command line library Note: I've split rte_mempool and rte_malloc as these two libraries are different enough. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-01-30 15:52:22 +00:00
Memory pool
M: Olivier Matz <olivier.matz@6wind.com>
maintainers: update for mempool Given its very good contributions to this library, add Andrew as official maintainer for librte_mempool. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: Andrew Rybchenko <arybchenko@solarflare.com>
2018-07-02 15:55:35 +00:00
M: Andrew Rybchenko <arybchenko@solarflare.com>
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: lib/librte_mempool/
mempool: move ring handler as a driver Moved from lib/librte_mempool, ring mempool is now an independent driver. Shared builds would now need to add librte_mempool_ring for: * ring_mp_mc * ring_sp_sc * ring_sp_mc * ring_mp_sc Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com> Acked-by: Olivier Matz <olivier.matz@6wind.com>
2017-03-31 05:35:36 +00:00
F: drivers/mempool/Makefile
F: drivers/mempool/ring/
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: doc/guides/prog_guide/mempool_lib.rst
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_mempool*
F: app/test/test_func_reentrancy.c
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
Ring queue
maintainers: update for ring library Honnappa and Konstantin contributed actively to the ring library and volunteered to replace myself as maintainers. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
2020-03-05 17:00:08 +00:00
M: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
M: Konstantin Ananyev <konstantin.ananyev@intel.com>
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: lib/librte_ring/
maintainers: dispatch more doc Documentation of build system, EAL and ring lib should be covered by the maintainers of the respective areas. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Olivier Matz <olivier.matz@6wind.com>
2015-02-04 08:08:45 +00:00
F: doc/guides/prog_guide/ring_lib.rst
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_ring*
F: app/test/test_func_reentrancy.c
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
stack: introduce stack library The rte_stack library provides an API for configuration and use of a bounded stack of pointers. Push and pop operations are MT-safe, allowing concurrent access, and the interface supports pushing and popping multiple pointers at a time. The library's interface is modeled after another DPDK data structure, rte_ring, and its lock-based implementation is derived from the stack mempool handler. An upcoming commit will migrate the stack mempool handler to rte_stack. Signed-off-by: Gage Eads <gage.eads@intel.com> Reviewed-by: Olivier Matz <olivier.matz@6wind.com> Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
2019-04-03 23:20:13 +00:00
Stack - EXPERIMENTAL
M: Gage Eads <gage.eads@intel.com>
M: Olivier Matz <olivier.matz@6wind.com>
F: lib/librte_stack/
mempool/stack: use stack library The new rte_stack library is derived from the mempool handler, so this commit removes duplicated code and simplifies the handler by migrating it to this new API. Signed-off-by: Gage Eads <gage.eads@intel.com> Reviewed-by: Olivier Matz <olivier.matz@6wind.com>
2019-04-03 23:20:14 +00:00
F: drivers/mempool/stack/
test/stack: check stack API stack_autotest performs positive and negative testing of the stack API, and exercises the push and pop datapath functions with all available lcores. Signed-off-by: Gage Eads <gage.eads@intel.com> Reviewed-by: Olivier Matz <olivier.matz@6wind.com>
2019-04-03 23:20:15 +00:00
F: app/test/test_stack*
stack: introduce stack library The rte_stack library provides an API for configuration and use of a bounded stack of pointers. Push and pop operations are MT-safe, allowing concurrent access, and the interface supports pushing and popping multiple pointers at a time. The library's interface is modeled after another DPDK data structure, rte_ring, and its lock-based implementation is derived from the stack mempool handler. An upcoming commit will migrate the stack mempool handler to rte_stack. Signed-off-by: Gage Eads <gage.eads@intel.com> Reviewed-by: Olivier Matz <olivier.matz@6wind.com> Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
2019-04-03 23:20:13 +00:00
F: doc/guides/prog_guide/stack_lib.rst
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
Packet buffer
maintainers: claim mbuf, mempool, ring, mk, kvargs, cmdline I'm volunteer to maintain the following components of dpdk: - mbuf packet api - mempool library - ring library - build system - kvargs - command line library Note: I've split rte_mempool and rte_malloc as these two libraries are different enough. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-01-30 15:52:22 +00:00
M: Olivier Matz <olivier.matz@6wind.com>
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: lib/librte_mbuf/
F: doc/guides/prog_guide/mbuf_lib.rst
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_mbuf.c
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
Ethernet API
maintainers: update email address Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
2017-04-18 21:36:51 +00:00
M: Thomas Monjalon <thomas@monjalon.net>
maintainers: update for ethdev Ferruh and Andrew are doing excellent reviews and contributions to ethdev API. They become official maintainers and responsibles of this major lib. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: Andrew Rybchenko <arybchenko@solarflare.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-06-29 14:58:57 +00:00
M: Ferruh Yigit <ferruh.yigit@intel.com>
M: Andrew Rybchenko <arybchenko@solarflare.com>
maintainers: fill git trees for net and crypto API The ethdev API (including rte_flow) is managed in the dpdk-next-net tree. The crypto API is managed in the dpdk-next-crypto tree. Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
2017-11-06 11:36:51 +00:00
T: git://dpdk.org/next/dpdk-next-net
ethdev: rename folder to library name Library folder name and output library name are same except a few flaws including librte_ether. This library is network device abstraction layer, the name "ethdev" fits better than "ether", and library & header files already named as ethdev. Also there is a rte_ether.h in the net library which can cause confusion. Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2018-04-26 21:25:59 +00:00
F: lib/librte_ethdev/
maintainers: fix script paths The directory scripts does not exist anymore. The files have been moved but some paths were not updated in the maintainers list. Fixes: 9a98f50e890b ("scripts: move to devtools") Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
2017-02-21 10:18:38 +00:00
F: devtools/test-null.sh
maintainers: add switch doc to ethdev section This patch adds file to "Ethernet API" section of MAINTAINERS file: F: doc/guides/prog_guide/switch_representation.rst Signed-off-by: Dekel Peled <dekelp@mellanox.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2019-04-01 11:05:14 +00:00
F: doc/guides/prog_guide/switch_representation.rst
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
ethdev: introduce generic flow API This new API supersedes all the legacy filter types described in rte_eth_ctrl.h. It is slightly higher level and as a result relies more on PMDs to process and validate flow rules. Benefits: - A unified API is easier to program for, applications do not have to be written for a specific filter type which may or may not be supported by the underlying device. - The behavior of a flow rule is the same regardless of the underlying device, applications do not need to be aware of hardware quirks. - Extensible by design, API/ABI breakage should rarely occur if at all. - Documentation is self-standing, no need to look up elsewhere. Existing filter types will be deprecated and removed in the near future. Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com> Acked-by: Olga Shern <olgas@mellanox.com>
2016-12-21 14:51:17 +00:00
Flow API
maintainers: update for flow API I volunteer to be co-maintainer for the rte_flow lib. Signed-off-by: Ori Kam <orika@mellanox.com> Acked-by: Adrien Mazarguil <adrien.mazarguil@6wind.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
2019-12-29 08:56:58 +00:00
M: Ori Kam <orika@mellanox.com>
maintainers: fill git trees for net and crypto API The ethdev API (including rte_flow) is managed in the dpdk-next-net tree. The crypto API is managed in the dpdk-next-crypto tree. Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
2017-11-06 11:36:51 +00:00
T: git://dpdk.org/next/dpdk-next-net
maintainers: fix responsibility of flow API bits The following commits lack MAINTAINERS entries for this mess. Fixes: 4d73b6fb9907 ("doc: add generic flow API guide") Fixes: 19c90af6285c ("app/testpmd: add flow command") Cc: stable@dpdk.org Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
2018-05-15 16:23:03 +00:00
F: app/test-pmd/cmdline_flow.c
F: doc/guides/prog_guide/rte_flow.rst
ethdev: rename folder to library name Library folder name and output library name are same except a few flaws including librte_ether. This library is network device abstraction layer, the name "ethdev" fits better than "ether", and library & header files already named as ethdev. Also there is a rte_ether.h in the net library which can cause confusion. Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2018-04-26 21:25:59 +00:00
F: lib/librte_ethdev/rte_flow*
ethdev: introduce generic flow API This new API supersedes all the legacy filter types described in rte_eth_ctrl.h. It is slightly higher level and as a result relies more on PMDs to process and validate flow rules. Benefits: - A unified API is easier to program for, applications do not have to be written for a specific filter type which may or may not be supported by the underlying device. - The behavior of a flow rule is the same regardless of the underlying device, applications do not need to be aware of hardware quirks. - Extensible by design, API/ABI breakage should rarely occur if at all. - Documentation is self-standing, no need to look up elsewhere. Existing filter types will be deprecated and removed in the near future. Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com> Acked-by: Olga Shern <olgas@mellanox.com>
2016-12-21 14:51:17 +00:00
ethdev: add traffic management API This patch introduces the generic ethdev API for the traffic manager capability, which includes: hierarchical scheduling, traffic shaping, congestion management, packet marking. Main features: - Exposed as ethdev plugin capability (similar to rte_flow) - Capability query API per port, per level and per node - Scheduling algorithms: Strict Priority (SP), Weighed Fair Queuing (WFQ) - Traffic shaping: single/dual rate, private (per node) and shared (by multiple nodes) shapers - Congestion management for hierarchy leaf nodes: algorithms of tail drop, head drop, WRED; private (per node) and shared (by multiple nodes) WRED contexts - Packet marking: IEEE 802.1q (VLAN DEI), IETF RFC 3168 (IPv4/IPv6 ECN for TCP and SCTP), IETF RFC 2597 (IPv4 / IPv6 DSCP) Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Acked-by: Balasubramanian Manoharan <balasubramanian.manoharan@caviumnetworks.com> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
2017-06-12 13:35:39 +00:00
Traffic Management API - EXPERIMENTAL
M: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
maintainers: set QoS git tree for some ethdev files The tree dpdk-next-tm does not exist anymore. Traffic management and metering APIs, which are part of ethdev, can be merged in the existing tree dpdk-next-qos. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2020-01-22 22:03:22 +00:00
T: git://dpdk.org/next/dpdk-next-qos
ethdev: rename folder to library name Library folder name and output library name are same except a few flaws including librte_ether. This library is network device abstraction layer, the name "ethdev" fits better than "ether", and library & header files already named as ethdev. Also there is a rte_ether.h in the net library which can cause confusion. Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2018-04-26 21:25:59 +00:00
F: lib/librte_ethdev/rte_tm*
ethdev: add traffic management API This patch introduces the generic ethdev API for the traffic manager capability, which includes: hierarchical scheduling, traffic shaping, congestion management, packet marking. Main features: - Exposed as ethdev plugin capability (similar to rte_flow) - Capability query API per port, per level and per node - Scheduling algorithms: Strict Priority (SP), Weighed Fair Queuing (WFQ) - Traffic shaping: single/dual rate, private (per node) and shared (by multiple nodes) shapers - Congestion management for hierarchy leaf nodes: algorithms of tail drop, head drop, WRED; private (per node) and shared (by multiple nodes) WRED contexts - Packet marking: IEEE 802.1q (VLAN DEI), IETF RFC 3168 (IPv4/IPv6 ECN for TCP and SCTP), IETF RFC 2597 (IPv4 / IPv6 DSCP) Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Acked-by: Balasubramanian Manoharan <balasubramanian.manoharan@caviumnetworks.com> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
2017-06-12 13:35:39 +00:00
ethdev: add API for traffic metering and policing This patch introduces new ethdev generic API for Traffic Metering and Policing (MTR), which is yet another standard RX offload for Ethernet devices. Similar to rte_flow and rte_tm APIs, the configuration of MTR objects is done in their own namespace (rte_mtr) within the librte_ether library. Main features: 1. Traffic metering: determine the color for the current packet (green, yellow, red) based on history maintained by the MTR object. Supported algorithms: srTCM (RFC 2697), trTCM (RFC 2698 and RFC 4115). 2. Policing (per meter output color actions): re-color the packet (keep or change the meter output color) or drop the packet. 3. Statistics 4. Capability API Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2017-10-13 12:22:16 +00:00
Traffic Metering and Policing API - EXPERIMENTAL
M: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
maintainers: set QoS git tree for some ethdev files The tree dpdk-next-tm does not exist anymore. Traffic management and metering APIs, which are part of ethdev, can be merged in the existing tree dpdk-next-qos. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2020-01-22 22:03:22 +00:00
T: git://dpdk.org/next/dpdk-next-qos
ethdev: rename folder to library name Library folder name and output library name are same except a few flaws including librte_ether. This library is network device abstraction layer, the name "ethdev" fits better than "ether", and library & header files already named as ethdev. Also there is a rte_ether.h in the net library which can cause confusion. Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2018-04-26 21:25:59 +00:00
F: lib/librte_ethdev/rte_mtr*
ethdev: add API for traffic metering and policing This patch introduces new ethdev generic API for Traffic Metering and Policing (MTR), which is yet another standard RX offload for Ethernet devices. Similar to rte_flow and rte_tm APIs, the configuration of MTR objects is done in their own namespace (rte_mtr) within the librte_ether library. Main features: 1. Traffic metering: determine the color for the current packet (green, yellow, red) based on history maintained by the MTR object. Supported algorithms: srTCM (RFC 2697), trTCM (RFC 2698 and RFC 4115). 2. Policing (per meter output color actions): re-color the packet (keep or change the meter output color) or drop the packet. 3. Statistics 4. Capability API Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2017-10-13 12:22:16 +00:00
bbdev: introduce wireless base band device lib - wireless baseband device (bbdev) library files - bbdev is tagged as EXPERIMENTAL - Makefiles and configuration macros definition - bbdev library is enabled by default - release notes of the initial version Signed-off-by: Amr Mokhtar <amr.mokhtar@intel.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-01-11 19:23:18 +00:00
Baseband API - EXPERIMENTAL
maintainers: claim maintainership of bbdev Reorg within Intel teams causing transfer of maintainership Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2019-06-17 18:21:28 +00:00
M: Nicolas Chautru <nicolas.chautru@intel.com>
maintainers: call out subtree for bbdev and security Commits for bbdev and security libraries are merged into the Next Crypto subtree. Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2018-04-13 08:14:39 +00:00
T: git://dpdk.org/next/dpdk-next-crypto
bbdev: introduce wireless base band device lib - wireless baseband device (bbdev) library files - bbdev is tagged as EXPERIMENTAL - Makefiles and configuration macros definition - bbdev library is enabled by default - release notes of the initial version Signed-off-by: Amr Mokhtar <amr.mokhtar@intel.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-01-11 19:23:18 +00:00
F: lib/librte_bbdev/
F: doc/guides/prog_guide/bbdev.rst
drivers: rename bbdev directory to baseband The drivers directory contains some sub-directories for each kind of device (or bus, mem): net, crypto, event, raw They are not suffixed with "dev" because it is obvious. For consistency, the sub-directory drivers/bbdev/ is renamed to drivers/baseband/. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: Amr Mokhtar <amr.mokhtar@intel.com>
2018-03-09 20:56:06 +00:00
F: drivers/baseband/
bb/null: add null base band device driver - 'bbdev_null' is a basic pmd that performs a minimalistic bbdev operation - useful for bbdev smoke testing and in measuring the overhead introduced by the bbdev library - 'bbdev_null' pmd is enabled by default Signed-off-by: Amr Mokhtar <amr.mokhtar@intel.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-01-11 19:23:19 +00:00
F: doc/guides/bbdevs/
app/testbbdev: add test application for bbdev - full test suite for bbdev - test App works seamlessly on all PMDs registered with bbdev framework - a python script is provided to make our life easier - supports execution of tests by parsing Test Vector files - test Vectors can be added/deleted/modified with no need for re-compilation - various tests can be executed: (a) Throughput test (b) Offload latency test (c) Operation latency test (d) Validation test (c) Sanity checks Signed-off-by: Amr Mokhtar <amr.mokhtar@intel.com>
2018-01-11 19:23:21 +00:00
F: app/test-bbdev/
F: doc/guides/tools/testbbdev.rst
examples/bbdev: add sample app - sample application performing a loop-back over ethernet using a bbbdev device - 'turbo_sw' PMD must be enabled for the app to be functional - a packet is received on an ethdev port -> enqueued for baseband encode operation -> dequeued -> enqueued for baseband decode operation-> dequeued -> compared with original signal -> looped-back to the ethdev port Signed-off-by: Amr Mokhtar <amr.mokhtar@intel.com>
2018-01-11 19:23:22 +00:00
F: examples/bbdev_app/
F: doc/guides/sample_app_ug/bbdev_app.rst
bbdev: introduce wireless base band device lib - wireless baseband device (bbdev) library files - bbdev is tagged as EXPERIMENTAL - Makefiles and configuration macros definition - bbdev library is enabled by default - release notes of the initial version Signed-off-by: Amr Mokhtar <amr.mokhtar@intel.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-01-11 19:23:18 +00:00
cryptodev: remove experimental label The cryptodev API was introduced in the DPDK 2.2 release. Since then it has - been reviewed and iterated for the DPDK 16.04 release - had extensive use by the l2fwd-crypto app, the ipsec-secgw example app, the test app. We believe it is now stable and the EXPERIMENTAL label should be removed. Signed-off-by: Fiona Trahe <fiona.trahe@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2016-04-06 11:05:08 +00:00
Crypto API
cryptodev: introduce API and framework for crypto devices This patch contains the initial proposed APIs and device framework for integrating crypto packet processing into DPDK. features include: - Crypto device configuration / management APIs - Definitions of supported cipher algorithms and operations. - Definitions of supported hash/authentication algorithms and operations. - Crypto session management APIs - Crypto operation data structures and APIs allocation of crypto operation structure used to specify the crypto operations to be performed on a particular mbuf. - Extension of mbuf to contain crypto operation data pointer and extra flags. - Burst enqueue / dequeue APIs for processing of crypto operations. Signed-off-by: Des O Dea <des.j.o.dea@intel.com> Signed-off-by: John Griffin <john.griffin@intel.com> Signed-off-by: Fiona Trahe <fiona.trahe@intel.com> Signed-off-by: Declan Doherty <declan.doherty@intel.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-11-25 13:25:12 +00:00
M: Declan Doherty <declan.doherty@intel.com>
maintainers: fill git trees for net and crypto API The ethdev API (including rte_flow) is managed in the dpdk-next-net tree. The crypto API is managed in the dpdk-next-crypto tree. Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
2017-11-06 11:36:51 +00:00
T: git://dpdk.org/next/dpdk-next-crypto
cryptodev: introduce API and framework for crypto devices This patch contains the initial proposed APIs and device framework for integrating crypto packet processing into DPDK. features include: - Crypto device configuration / management APIs - Definitions of supported cipher algorithms and operations. - Definitions of supported hash/authentication algorithms and operations. - Crypto session management APIs - Crypto operation data structures and APIs allocation of crypto operation structure used to specify the crypto operations to be performed on a particular mbuf. - Extension of mbuf to contain crypto operation data pointer and extra flags. - Burst enqueue / dequeue APIs for processing of crypto operations. Signed-off-by: Des O Dea <des.j.o.dea@intel.com> Signed-off-by: John Griffin <john.griffin@intel.com> Signed-off-by: Fiona Trahe <fiona.trahe@intel.com> Signed-off-by: Declan Doherty <declan.doherty@intel.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-11-25 13:25:12 +00:00
F: lib/librte_cryptodev/
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_cryptodev*
examples/l2fwd-crypto: add sample application This patch creates a new sample applicaiton based off the l2fwd application which performs specified crypto operations on IP packet payloads which are forwarding. Signed-off-by: Declan Doherty <declan.doherty@intel.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-11-25 13:25:17 +00:00
F: examples/l2fwd-crypto/
cryptodev: introduce API and framework for crypto devices This patch contains the initial proposed APIs and device framework for integrating crypto packet processing into DPDK. features include: - Crypto device configuration / management APIs - Definitions of supported cipher algorithms and operations. - Definitions of supported hash/authentication algorithms and operations. - Crypto session management APIs - Crypto operation data structures and APIs allocation of crypto operation structure used to specify the crypto operations to be performed on a particular mbuf. - Extension of mbuf to contain crypto operation data pointer and extra flags. - Burst enqueue / dequeue APIs for processing of crypto operations. Signed-off-by: Des O Dea <des.j.o.dea@intel.com> Signed-off-by: John Griffin <john.griffin@intel.com> Signed-off-by: Fiona Trahe <fiona.trahe@intel.com> Signed-off-by: Declan Doherty <declan.doherty@intel.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-11-25 13:25:12 +00:00
security: remove experimental tag rte_security has been experimental since DPDK 17.11 release. Now the library has matured and expermental tag is removed in this patch. Signed-off-by: Akhil Goyal <akhil.goyal@nxp.com> Acked-by: Anoob Joseph <anoob.joseph@caviumnetworks.com> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com> Acked-by: Boris Pismenny <borisp@mellanox.com>
2018-11-13 11:28:21 +00:00
Security API
security: introduce security API and framework rte_security library provides APIs for security session create/free for protocol offload or offloaded crypto operation to ethernet device. Signed-off-by: Akhil Goyal <akhil.goyal@nxp.com> Signed-off-by: Boris Pismenny <borisp@mellanox.com> Signed-off-by: Radu Nicolau <radu.nicolau@intel.com> Signed-off-by: Declan Doherty <declan.doherty@intel.com> Signed-off-by: Aviad Yehezkel <aviadye@mellanox.com>
2017-10-25 15:07:23 +00:00
M: Akhil Goyal <akhil.goyal@nxp.com>
M: Declan Doherty <declan.doherty@intel.com>
maintainers: call out subtree for bbdev and security Commits for bbdev and security libraries are merged into the Next Crypto subtree. Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2018-04-13 08:14:39 +00:00
T: git://dpdk.org/next/dpdk-next-crypto
security: introduce security API and framework rte_security library provides APIs for security session create/free for protocol offload or offloaded crypto operation to ethernet device. Signed-off-by: Akhil Goyal <akhil.goyal@nxp.com> Signed-off-by: Boris Pismenny <borisp@mellanox.com> Signed-off-by: Radu Nicolau <radu.nicolau@intel.com> Signed-off-by: Declan Doherty <declan.doherty@intel.com> Signed-off-by: Aviad Yehezkel <aviadye@mellanox.com>
2017-10-25 15:07:23 +00:00
F: lib/librte_security/
doc: add details of security library Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com> Signed-off-by: Akhil Goyal <akhil.goyal@nxp.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2017-10-25 15:07:24 +00:00
F: doc/guides/prog_guide/rte_security.rst
test/security: introduce security lib tests This patch introduces set of unit tests of librte_security API functions. Tests are added to dpdk-test application and can be run with "security_autotest" runtime command. This is the first patch in the series of patches as adding all test cases for all API functions in a single patch would make it unreadable. This patch defines structure of the file and necessary test framework initialization. It also contains first subset of unit tests for rte_security_session_create API function. Structure of the tests file is following: - macros for making tests more readable; - mockup structures and functions for rte_security_ops; - test suite and test cases setup and teardown functions; - tests functions; - declaration of testcases. Signed-off-by: Lukasz Wojciechowski <l.wojciechow@partner.samsung.com> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
2020-04-09 17:24:54 +00:00
F: app/test/test_security.c
security: introduce security API and framework rte_security library provides APIs for security session create/free for protocol offload or offloaded crypto operation to ethernet device. Signed-off-by: Akhil Goyal <akhil.goyal@nxp.com> Signed-off-by: Boris Pismenny <borisp@mellanox.com> Signed-off-by: Radu Nicolau <radu.nicolau@intel.com> Signed-off-by: Declan Doherty <declan.doherty@intel.com> Signed-off-by: Aviad Yehezkel <aviadye@mellanox.com>
2017-10-25 15:07:23 +00:00
compressdev: add basic device management Add basic functions to manage compress devices, including driver and device allocation, and the basic interface with compressdev PMDs. Signed-off-by: Fiona Trahe <fiona.trahe@intel.com> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Signed-off-by: Shally Verma <shally.verma@caviumnetworks.com> Signed-off-by: Ashish Gupta <ashish.gupta@caviumnetworks.com>
2018-04-27 13:23:54 +00:00
Compression API - EXPERIMENTAL
M: Fiona Trahe <fiona.trahe@intel.com>
maintainers: update Cavium email ids Following Marvell's acquisition of Cavium, we need to update all the Cavium maintainer's entries to point to our new e-mail addresses. Update maintainers as they are no longer working for Cavium. Thanks to Harish Patil for his support and development of our various dpdk drivers. Signed-off-by: Jerin Jacob <jerinj@marvell.com>
2018-12-16 15:43:25 +00:00
M: Ashish Gupta <ashish.gupta@marvell.com>
compressdev: add basic device management Add basic functions to manage compress devices, including driver and device allocation, and the basic interface with compressdev PMDs. Signed-off-by: Fiona Trahe <fiona.trahe@intel.com> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Signed-off-by: Shally Verma <shally.verma@caviumnetworks.com> Signed-off-by: Ashish Gupta <ashish.gupta@caviumnetworks.com>
2018-04-27 13:23:54 +00:00
T: git://dpdk.org/next/dpdk-next-crypto
F: lib/librte_compressdev/
compress/isal: add skeleton ISA-L compression PMD Adding basic skeleton of the ISA-L compression driver. No compression functionality, but lays the foundation for operations in the rest of the patchset. The ISA-L compression driver utilizes Intel's ISA-L compression library and compressdev API. Signed-off-by: Lee Daly <lee.daly@intel.com> Reviewed-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2018-05-09 16:14:26 +00:00
F: drivers/compress/
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_compressdev*
doc: add compressdev library guide Add section in programmer’s guide for Compressdev library. Signed-off-by: Shally Verma <shally.verma@caviumnetworks.com> Signed-off-by: Sunila Sahu <sunila.sahu@caviumnetworks.com> Signed-off-by: Ashish Gupta <ashish.gupta@caviumnetworks.com>
2018-04-27 13:24:07 +00:00
F: doc/guides/prog_guide/compressdev.rst
doc: add compression driver and ISA-L PMD guides This adds general compression drivers feature guide as well as the ISA-L PMD documentation and guide. Signed-off-by: Lee Daly <lee.daly@intel.com> Reviewed-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2018-05-09 16:14:35 +00:00
F: doc/guides/compressdevs/features/default.ini
compressdev: add basic device management Add basic functions to manage compress devices, including driver and device allocation, and the basic interface with compressdev PMDs. Signed-off-by: Fiona Trahe <fiona.trahe@intel.com> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Signed-off-by: Shally Verma <shally.verma@caviumnetworks.com> Signed-off-by: Ashish Gupta <ashish.gupta@caviumnetworks.com>
2018-04-27 13:23:54 +00:00
eventdev: remove experimental label The eventdev API was introduced in DPDK 17.05 release. Since then it - has been reviewed and iterated for 17.08, 17.11 releases - three drivers were implemented using the API. - introduced another subsystem like service core and ethdev-eventdev Rx adapter APIs to abstract the difference between HW and SW eventdev implementations in a transparent way. - had extensive use by the app/test-eventdev/ and examples/eventdev_pipeline_sw_pmd/ I believe the API is now stable and the EXPERIMENTAL label should be removed. Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Acked-by: Gage Eads <gage.eads@intel.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2017-10-16 10:32:55 +00:00
Eventdev API
maintainers: update Cavium email ids Following Marvell's acquisition of Cavium, we need to update all the Cavium maintainer's entries to point to our new e-mail addresses. Update maintainers as they are no longer working for Cavium. Thanks to Harish Patil for his support and development of our various dpdk drivers. Signed-off-by: Jerin Jacob <jerinj@marvell.com>
2018-12-16 15:43:25 +00:00
M: Jerin Jacob <jerinj@marvell.com>
eventdev: introduce event driven programming model In a polling model, lcores poll ethdev ports and associated rx queues directly to look for packet. In an event driven model, by contrast, lcores call the scheduler that selects packets for them based on programmer-specified criteria. Eventdev library adds support for event driven programming model, which offer applications automatic multicore scaling, dynamic load balancing, pipelining, packet ingress order maintenance and synchronization services to simplify application packet processing. By introducing event driven programming model, DPDK can support both polling and event driven programming models for packet processing, and applications are free to choose whatever model (or combination of the two) that best suits their needs. This patch adds the eventdev specification header file. Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2016-11-18 02:00:38 +00:00
T: git://dpdk.org/next/dpdk-next-eventdev
F: lib/librte_eventdev/
event/skeleton: add skeleton eventdev driver The skeleton driver facilitates, bootstrapping the new eventdev driver and creates a platform to verify the northbound eventdev common code. The driver supports both VDEV and PCI based eventdev devices. Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2016-11-18 05:45:01 +00:00
F: drivers/event/skeleton/
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_eventdev.c
examples/l3fwd: add framework for event device Add framework to enable event device as a producer of packets. To switch between event mode and poll mode the following options have been added: `--mode="eventdev"` or `--mode="poll"` Allow the user to select the schedule type to be either RTE_SCHED_TYPE_ORDERED, RTE_SCHED_TYPE_ATOMIC or RTE_SCHED_TYPE_PARALLEL through: `--eventq-sched="ordered"` or `--eventq-sched="atomic"` or `--eventq-sched="parallel"` Allow the user to specify the number of Rx queues to be connected to event queue using: `--event-eth-rxqs` Poll mode is still the default operation mode. Signed-off-by: Sunil Kumar Kori <skori@marvell.com> Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com> Acked-by: Jerin Jacob <jerinj@marvell.com>
2020-01-28 05:34:55 +00:00
F: examples/l3fwd/l3fwd_event*
eventdev: introduce event driven programming model In a polling model, lcores poll ethdev ports and associated rx queues directly to look for packet. In an event driven model, by contrast, lcores call the scheduler that selects packets for them based on programmer-specified criteria. Eventdev library adds support for event driven programming model, which offer applications automatic multicore scaling, dynamic load balancing, pipelining, packet ingress order maintenance and synchronization services to simplify application packet processing. By introducing event driven programming model, DPDK can support both polling and event driven programming models for packet processing, and applications are free to choose whatever model (or combination of the two) that best suits their needs. This patch adds the eventdev specification header file. Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2016-11-18 02:00:38 +00:00
eventdev: change Rx adapter callback and stats structure Replace the mbuf pointer array in the event eth Rx adapter callback with an event array. Using an event array allows the application to change attributes of the events enqueued by the SW adapter. The callback can drop packets and populate a callback argument with the number of dropped packets. Add a Rx adapter stats field to keep track of the total number of dropped packets. This commit removes the experimental tags from the callback and stats APIs, the experimental tag from eventdev is also removed and eventdev functions become part of the main DPDK API/ABI. Signed-off-by: Nikhil Rao <nikhil.rao@intel.com> Acked-by: Jerin Jacob <jerinj@marvell.com>
2019-06-24 23:16:02 +00:00
Eventdev Ethdev Rx Adapter API
eventdev: add eth Rx adapter API Add common APIs for configuring packet transfer from ethernet Rx queues to event devices across HW & SW packet transfer mechanisms. A detailed description of the adapter is contained in the header's comments. Signed-off-by: Nikhil Rao <nikhil.rao@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2017-10-10 22:21:34 +00:00
M: Nikhil Rao <nikhil.rao@intel.com>
T: git://dpdk.org/next/dpdk-next-eventdev
F: lib/librte_eventdev/*eth_rx_adapter*
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_event_eth_rx_adapter.c
doc: add event eth Rx adapter guide Add programmer's guide doc to explain the use of the Event Ethernet Rx Adapter library. Signed-off-by: Nikhil Rao <nikhil.rao@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2017-10-24 09:13:29 +00:00
F: doc/guides/prog_guide/event_ethernet_rx_adapter.rst
eventdev: promote adapter functions as stable Promote the adapter functions and rte_event_port_unlinks_in_progress() as stable as it's been added for a while now and multiple drivers and test application like test-eventdev has been tested using the adapter APIs. Signed-off-by: Jerin Jacob <jerinj@marvell.com> Acked-by: Abhinandan Gujjar <abhinandan.gujjar@intel.com> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
2019-04-19 12:10:40 +00:00
Eventdev Ethdev Tx Adapter API
eventdev: add eth Tx adapter APIs The ethernet Tx adapter abstracts the transmit stage of an event driven packet processing application. The transmit stage may be implemented with eventdev PMD support or use a rte_service function implemented in the adapter. These APIs provide a common configuration and control interface and an transmit API for the eventdev PMD implementation. The transmit port is specified using mbuf::port. The transmit queue is specified using the rte_event_eth_tx_adapter_txq_set() function. Signed-off-by: Nikhil Rao <nikhil.rao@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2018-09-20 17:41:12 +00:00
M: Nikhil Rao <nikhil.rao@intel.com>
T: git://dpdk.org/next/dpdk-next-eventdev
F: lib/librte_eventdev/*eth_tx_adapter*
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_event_eth_tx_adapter.c
doc: add event eth Tx adapter guide Add programmer's guide doc to explain the use of the Event Ethernet Tx Adapter library. Signed-off-by: Nikhil Rao <nikhil.rao@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2018-09-20 17:41:16 +00:00
F: doc/guides/prog_guide/event_ethernet_tx_adapter.rst
eventdev: add eth Tx adapter APIs The ethernet Tx adapter abstracts the transmit stage of an event driven packet processing application. The transmit stage may be implemented with eventdev PMD support or use a rte_service function implemented in the adapter. These APIs provide a common configuration and control interface and an transmit API for the eventdev PMD implementation. The transmit port is specified using mbuf::port. The transmit queue is specified using the rte_event_eth_tx_adapter_txq_set() function. Signed-off-by: Nikhil Rao <nikhil.rao@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2018-09-20 17:41:12 +00:00
eventdev: promote adapter functions as stable Promote the adapter functions and rte_event_port_unlinks_in_progress() as stable as it's been added for a while now and multiple drivers and test application like test-eventdev has been tested using the adapter APIs. Signed-off-by: Jerin Jacob <jerinj@marvell.com> Acked-by: Abhinandan Gujjar <abhinandan.gujjar@intel.com> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
2019-04-19 12:10:40 +00:00
Eventdev Timer Adapter API
eventdev: introduce event timer adapter Event devices can be coupled with various components to provide new event sources by using event adapters. The event timer adapter is one such adapter; it bridges event devices and timer mechanisms. This library extends the event-driven programming model by introducing a new type of event that represents a timer expiration, and it provides APIs with which adapters can be created or destroyed and event timers can be armed and canceled. Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com> Signed-off-by: Erik Gabriel Carrillo <erik.g.carrillo@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2018-04-04 21:51:06 +00:00
M: Erik Gabriel Carrillo <erik.g.carrillo@intel.com>
T: git://dpdk.org/next/dpdk-next-eventdev
F: lib/librte_eventdev/*timer_adapter*
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_event_timer_adapter.c
doc: add event timer adapter guide Signed-off-by: Erik Gabriel Carrillo <erik.g.carrillo@intel.com> Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2018-04-04 21:51:13 +00:00
F: doc/guides/prog_guide/event_timer_adapter.rst
eventdev: introduce event timer adapter Event devices can be coupled with various components to provide new event sources by using event adapters. The event timer adapter is one such adapter; it bridges event devices and timer mechanisms. This library extends the event-driven programming model by introducing a new type of event that represents a timer expiration, and it provides APIs with which adapters can be created or destroyed and event timers can be armed and canceled. Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com> Signed-off-by: Erik Gabriel Carrillo <erik.g.carrillo@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2018-04-04 21:51:06 +00:00
eventdev: promote adapter functions as stable Promote the adapter functions and rte_event_port_unlinks_in_progress() as stable as it's been added for a while now and multiple drivers and test application like test-eventdev has been tested using the adapter APIs. Signed-off-by: Jerin Jacob <jerinj@marvell.com> Acked-by: Abhinandan Gujjar <abhinandan.gujjar@intel.com> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
2019-04-19 12:10:40 +00:00
Eventdev Crypto Adapter API
eventdev: introduce event crypto adapter This patch introduces event crypto adapter APIs. It also provides information on working model/adapter modes & their usage. Application is expected to use this interface to transfer packets between the crypto device & the event device. Signed-off-by: Abhinandan Gujjar <abhinandan.gujjar@intel.com> Signed-off-by: Nikhil Rao <nikhil.rao@intel.com> Signed-off-by: Gage Eads <gage.eads@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
2018-05-09 08:17:57 +00:00
M: Abhinandan Gujjar <abhinandan.gujjar@intel.com>
T: git://dpdk.org/next/dpdk-next-eventdev
F: lib/librte_eventdev/*crypto_adapter*
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_event_crypto_adapter.c
doc: add event crypto adapter guide Add entries in the programmer's guide, API index, maintainer's file and release notes for the event crypto adapter. Signed-off-by: Abhinandan Gujjar <abhinandan.gujjar@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
2018-05-09 08:18:01 +00:00
F: doc/guides/prog_guide/event_crypto_adapter.rst
eventdev: introduce event crypto adapter This patch introduces event crypto adapter APIs. It also provides information on working model/adapter modes & their usage. Application is expected to use this interface to transfer packets between the crypto device & the event device. Signed-off-by: Abhinandan Gujjar <abhinandan.gujjar@intel.com> Signed-off-by: Nikhil Rao <nikhil.rao@intel.com> Signed-off-by: Gage Eads <gage.eads@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
2018-05-09 08:17:57 +00:00
rawdev: introduce raw device library Each device in DPDK has a type associated with it - ethernet, crypto, event etc. This patch introduces 'rawdevice' which is a generic type of device, not currently handled out-of-the-box by DPDK. A device which can be scanned on an installed bus (pci, fslmc, ...) or instantiated through devargs, can be interfaced using standardized APIs just like other standardized devices. This library introduces an API set which can be plugged on the northbound side to the application layer, and on the southbound side to the driver layer. The APIs of rawdev library exposes some generic operations which can enable configuration and I/O with the raw devices. Using opaque data (pointer) as API arguments, library allows a high flexibility for application and driver implementation. This patch introduces basic device operations like start, stop, reset, queue and info support. Subsequent patches would introduce other operations like buffer enqueue/dequeue and firmware support. Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com>
2018-01-31 09:13:09 +00:00
Raw device API - EXPERIMENTAL
maintainers: update for rawdev Replace rawdev maintainer. Shreyansh is no longer with NXP. Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com> Acked-by: Nipun Gupta <nipun.gupta@nxp.com>
2020-03-30 05:17:29 +00:00
M: Nipun Gupta <nipun.gupta@nxp.com>
rawdev: introduce raw device library Each device in DPDK has a type associated with it - ethernet, crypto, event etc. This patch introduces 'rawdevice' which is a generic type of device, not currently handled out-of-the-box by DPDK. A device which can be scanned on an installed bus (pci, fslmc, ...) or instantiated through devargs, can be interfaced using standardized APIs just like other standardized devices. This library introduces an API set which can be plugged on the northbound side to the application layer, and on the southbound side to the driver layer. The APIs of rawdev library exposes some generic operations which can enable configuration and I/O with the raw devices. Using opaque data (pointer) as API arguments, library allows a high flexibility for application and driver implementation. This patch introduces basic device operations like start, stop, reset, queue and info support. Subsequent patches would introduce other operations like buffer enqueue/dequeue and firmware support. Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com>
2018-01-31 09:13:09 +00:00
M: Hemant Agrawal <hemant.agrawal@nxp.com>
F: lib/librte_rawdev/
drivers/raw: remove rawdev from directory names The ifpga and skeleton rawdev drivers included "rawdev" in their directory names, which was superfluous given that they were in the drivers/raw directory. Shorten the names via this patch. For meson builds, this will rename the final library .so/.a files produced, but those will be renamed again later via a patch to standardize rawdev names. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
2019-07-05 09:34:00 +00:00
F: drivers/raw/skeleton/
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_rawdev.c
doc: add rawdev library guide and doxygen page Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com>
2018-01-31 09:13:18 +00:00
F: doc/guides/prog_guide/rawdev.rst
rawdev: introduce raw device library Each device in DPDK has a type associated with it - ethernet, crypto, event etc. This patch introduces 'rawdevice' which is a generic type of device, not currently handled out-of-the-box by DPDK. A device which can be scanned on an installed bus (pci, fslmc, ...) or instantiated through devargs, can be interfaced using standardized APIs just like other standardized devices. This library introduces an API set which can be plugged on the northbound side to the application layer, and on the southbound side to the driver layer. The APIs of rawdev library exposes some generic operations which can enable configuration and I/O with the raw devices. Using opaque data (pointer) as API arguments, library allows a high flexibility for application and driver implementation. This patch introduces basic device operations like start, stop, reset, queue and info support. Subsequent patches would introduce other operations like buffer enqueue/dequeue and firmware support. Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com>
2018-01-31 09:13:09 +00:00
eventdev: add eth Rx adapter API Add common APIs for configuring packet transfer from ethernet Rx queues to event devices across HW & SW packet transfer mechanisms. A detailed description of the adapter is contained in the header's comments. Signed-off-by: Nikhil Rao <nikhil.rao@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2017-10-10 22:21:34 +00:00
mempool/bucket: implement bucket mempool manager The manager provides a way to allocate physically and virtually contiguous set of objects. Signed-off-by: Artem V. Andreev <artem.andreev@oktetlabs.ru> Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com>
2018-04-26 10:59:19 +00:00
Memory Pool Drivers
-------------------
Bucket memory pool
M: Artem V. Andreev <artem.andreev@oktetlabs.ru>
M: Andrew Rybchenko <arybchenko@solarflare.com>
F: drivers/mempool/bucket/
common/octeontx2: add build infrastructure and HW definition Add the make and meson based build infrastructure along with HW definition header file. This patch adds skeleton otx2_mbox.c file to make sure all header files are intact, subsequent patches add content to otx2_mbox.c This patch also updates CONFIG_RTE_MAX_VFIO_GROUPS value to 128 as the system can have up to 128 PFs/VFs. For octeontx2 meson build target, CONFIG_RTE_MAX_VFIO_GROUPS defined as 128 so no additional changes required. Signed-off-by: Jerin Jacob <jerinj@marvell.com> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
2019-06-22 13:23:51 +00:00
Marvell OCTEON TX2
M: Jerin Jacob <jerinj@marvell.com>
M: Nithin Dabilpuram <ndabilpuram@marvell.com>
F: drivers/common/octeontx2/
mempool/octeontx2: add build infra and device probe Add the make and meson based build infrastructure along with the mempool(NPA) device probe. Signed-off-by: Jerin Jacob <jerinj@marvell.com> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
2019-06-22 13:24:06 +00:00
F: drivers/mempool/octeontx2/
doc: add Marvell OCTEON TX2 platform guide Platform specific guide for Marvell OCTEON TX2 SoC is added. Signed-off-by: Jerin Jacob <jerinj@marvell.com> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com> Signed-off-by: Shally Verma <shallyv@marvell.com> Signed-off-by: Vivek Sharma <viveksharma@marvell.com>
2019-06-22 13:24:05 +00:00
F: doc/guides/platform/img/octeontx2_*
F: doc/guides/platform/octeontx2.rst
doc: add Marvell OCTEON TX2 mempool guide Add Marvell OCTEON TX2 mempool documentation. Signed-off-by: Jerin Jacob <jerinj@marvell.com> Signed-off-by: Vivek Sharma <viveksharma@marvell.com> Signed-off-by: Vamsi Attunuru <vattunuru@marvell.com> Signed-off-by: Nithin Dabilpuram <ndabilpuram@marvell.com>
2019-06-22 13:24:17 +00:00
F: doc/guides/mempool/octeontx2.rst
common/octeontx2: add build infrastructure and HW definition Add the make and meson based build infrastructure along with HW definition header file. This patch adds skeleton otx2_mbox.c file to make sure all header files are intact, subsequent patches add content to otx2_mbox.c This patch also updates CONFIG_RTE_MAX_VFIO_GROUPS value to 128 as the system can have up to 128 PFs/VFs. For octeontx2 meson build target, CONFIG_RTE_MAX_VFIO_GROUPS defined as 128 so no additional changes required. Signed-off-by: Jerin Jacob <jerinj@marvell.com> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
2019-06-22 13:23:51 +00:00
mempool/bucket: implement bucket mempool manager The manager provides a way to allocate physically and virtually contiguous set of objects. Signed-off-by: Artem V. Andreev <artem.andreev@oktetlabs.ru> Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com>
2018-04-26 10:59:19 +00:00
pci: introduce library and driver The PCI lib defines the types and methods allowing to use PCI elements. The PCI bus implements a bus driver for PCI devices by constructing rte_bus elements using the PCI lib. Move the relevant code out of the EAL to its expected place. Libraries, drivers, unit tests and applications are updated to use the new rte_bus_pci.h header when necessary. Signed-off-by: Gaetan Rivet <gaetan.rivet@6wind.com>
2017-10-26 10:06:08 +00:00
Bus Drivers
-----------
bus/ifpga: add Intel FPGA bus library Defined FPGA-BUS for Acceleration Drivers of AFUs 1. FPGA PCI Scan (1st Scan) follows DPDK UIO/VFIO PCI Scan Process, probe Intel FPGA Rawdev Driver, it will be covered in following patches. 2. AFU Scan(2nd Scan) bind DPDK driver to FPGA Partial-Bitstream. This scan is trigged by hotplug of IFPGA Rawdev probe, in this scan the AFUs will be created and their drivers are also probed. This patch will introduce rte_afu_device which describe the AFU device listed in the FPGA-BUS. Signed-off-by: Rosen Xu <rosen.xu@intel.com> Signed-off-by: Tianfei Zhang <tianfei.zhang@intel.com> Reviewed-by: Qi Zhang <qi.z.zhang@intel.com>
2018-05-11 08:31:29 +00:00
Intel FPGA bus
M: Rosen Xu <rosen.xu@intel.com>
F: drivers/bus/ifpga/
maintainers: move NXP bus drivers in related section A bus maintainers section has been introduced in 17.11. Let's move all bus drivers in the same place. Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
2017-11-15 00:42:24 +00:00
NXP buses
M: Hemant Agrawal <hemant.agrawal@nxp.com>
maintainers: claim maintainership of NXP net PMDs Shreyansh is no longer with NXP. Pankaj is no longer working on DPDK. Signed-off-by: Sachin Saxena <sachin.saxena@nxp.com> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
2019-07-15 11:38:30 +00:00
M: Sachin Saxena <sachin.saxena@nxp.com>
common/dpaax: add library for PA/VA translation table A common library, valid for dpaaX drivers, which is used to maintain a local copy of PA->VA translations. In case of physical addressing mode (one of the option for FSLMC, and only option for DPAA bus), the addresses of descriptors Rx'd are physical. These need to be converted into equivalent VA for rte_mbuf and other similar calls. Using the rte_mem_virt2iova or rte_mem_virt2phy is expensive. This library is an attempt to reduce the overall cost associated with this translation. A small table is maintained, containing continuous entries representing a continguous physical range. Each of these entries stores the equivalent VA, which is fed during mempool creation, or memory allocation/deallocation callbacks. Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com>
2018-10-15 12:01:54 +00:00
F: drivers/common/dpaax/
maintainers: move NXP bus drivers in related section A bus maintainers section has been introduced in 17.11. Let's move all bus drivers in the same place. Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
2017-11-15 00:42:24 +00:00
F: drivers/bus/dpaa/
F: drivers/bus/fslmc/
pci: introduce library and driver The PCI lib defines the types and methods allowing to use PCI elements. The PCI bus implements a bus driver for PCI devices by constructing rte_bus elements using the PCI lib. Move the relevant code out of the EAL to its expected place. Libraries, drivers, unit tests and applications are updated to use the new rte_bus_pci.h header when necessary. Signed-off-by: Gaetan Rivet <gaetan.rivet@6wind.com>
2017-10-26 10:06:08 +00:00
PCI bus driver
F: drivers/bus/pci/
bus/vdev: move code from EAL into a new driver Move the vdev bus from lib/librte_eal to drivers/bus. As the crypto vdev helper function refers to data structure in rte_vdev.h, so we move those helper function into drivers/bus too. Signed-off-by: Jianfeng Tan <jianfeng.tan@intel.com>
2017-11-07 06:54:21 +00:00
VDEV bus driver
F: drivers/bus/vdev/
bus/vmbus: add Hyper-V virtual bus support This patch adds support for an additional bus type Virtual Machine BUS (VMBUS) on Microsoft Hyper-V in Windows 10, Windows Server 2016 and Azure. Most of this code was extracted from FreeBSD and some of this is from earlier code donated by Brocade. Only Linux is supported at present, but the code is split to allow future FreeBSD and Windows support. The bus support relies on the uio_hv_generic driver from Linux kernel 4.16. Multiple queue support requires additional sysfs interfaces which is in kernel 5.0 (a.k.a 4.17). Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
2018-07-13 17:06:42 +00:00
VMBUS bus driver
M: Stephen Hemminger <sthemmin@microsoft.com>
F: drivers/bus/vmbus/
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
maintainers: split networking and crypto drivers There are now 2 different sections for drivers/net/ and drivers/crypto/. It makes possible to declare some dedicated git trees. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2016-07-20 10:34:45 +00:00
Networking Drivers
------------------
maintainers: add staging tree for network drivers Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2016-11-10 12:14:40 +00:00
M: Ferruh Yigit <ferruh.yigit@intel.com>
T: git://dpdk.org/next/dpdk-next-net
maintainers: add drivers features files Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-05-10 13:33:50 +00:00
F: doc/guides/nics/features/default.ini
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
Link bonding
maintainers: claim responsibility for bonding PMD Add myself as co-maintainer for bonding driver and related materials. Signed-off-by: Chas Williams <chas3@att.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-05-30 14:44:39 +00:00
M: Chas Williams <chas3@att.com>
maintainers: update for bonding Adding Xavier as additional maintainer to bonding. Signed-off-by: Wei Hu (Xavier) <xavier.huwei@huawei.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Chas Williams <chas3@att.com>
2020-05-18 11:20:09 +00:00
M: Wei Hu (Xavier) <xavier.huwei@huawei.com>
bond: move to drivers/net/ Move bonded ethdev pmd to drivers/net Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: John McNamara <john.mcnamara@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-05-15 15:56:48 +00:00
F: drivers/net/bonding/
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: doc/guides/prog_guide/link_bonding_poll_mode_drv_lib.rst
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_link_bonding*
examples/bond: add example application for link bonding mode 6 This patch contains an example for link bonding mode 6. It interact with user by a command prompt. Available commands are: Start - starts ARP_thread which respond to ARP_requests and sends ARP_updates (this Is enabled by default after startup), Stop -stops ARP_thread, Send count ip - send count ARP requests for IP, Show - prints basic bond information, like IPv4 statistics from clients Help, Quit. The best way to test mode 6 is to use this example together with previous patch: [PATCH 3/4] bond: add debug info for mode 6 link bonding. Connect clients thru switch to bonding machine and send: arping -c 1 bond_ip or generate IPv4 traffic to bond_ip (IPv4 traffic from different clients should be then balanced on slaves in round robin manner). Signed-off-by: Michal Jastrzebski <michalx.k.jastrzebski@intel.com> Signed-off-by: Maciej Gajdzica <maciejx.t.gajdzica@intel.com> Acked-by: Declan Doherty <declan.doherty@intel.com>
2015-02-20 16:09:21 +00:00
F: examples/bond/
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
Linux KNI
maintainers: claim responsibility for KNI Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Helin Zhang <helin.zhang@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2016-07-07 11:00:29 +00:00
M: Ferruh Yigit <ferruh.yigit@intel.com>
move kernel modules directories This patch moves the kernel modules code from EAL to a common place. - Separate the kernel module code from user space code. Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com> Tested-by: Bruce Richardson <bruce.richardson@intel.com>
2018-02-22 06:09:05 +00:00
F: kernel/linux/kni/
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: lib/librte_kni/
F: doc/guides/prog_guide/kernel_nic_interface.rst
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_kni.c
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: examples/kni/
F: doc/guides/sample_app_ug/kernel_nic_interface.rst
Linux AF_PACKET
maintainers: claim responsibility for Linux AF_PACKET PMD Signed-off-by: John W. Linville <linville@tuxdriver.com> Acked-by: Neil Horman <nhorman@tuxdriver.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-01-23 18:12:25 +00:00
M: John W. Linville <linville@tuxdriver.com>
af_packet: move to drivers/net/ move af_packet pmd to drivers/net directory Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: John McNamara <john.mcnamara@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-05-15 15:56:47 +00:00
F: drivers/net/af_packet/
maintainers: add drivers features files Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-05-10 13:33:50 +00:00
F: doc/guides/nics/features/afpacket.ini
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
net/af_xdp: introduce AF_XDP PMD Add a new PMD driver for AF_XDP which is a proposed faster version of AF_PACKET interface in Linux. More info about AF_XDP, please refer to [1] [2]. This is the vanilla version PMD which just uses a raw buffer registered as the umem. [1] https://fosdem.org/2018/schedule/event/af_xdp/ [2] https://lwn.net/Articles/745934/ Signed-off-by: Xiaolong Ye <xiaolong.ye@intel.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Luca Boccassi <bluca@debian.org> Reviewed-by: Stephen Hemminger <stephen@networkplumber.org>
2019-04-04 08:51:13 +00:00
Linux AF_XDP
M: Xiaolong Ye <xiaolong.ye@intel.com>
M: Qi Zhang <qi.z.zhang@intel.com>
F: drivers/net/af_xdp/
F: doc/guides/nics/af_xdp.rst
F: doc/guides/nics/features/af_xdp.ini
ena: introduce documentation Signed-off-by: Alexander Matushevsky <matua@amazon.com> Signed-off-by: Jan Medala <jan@semihalf.com> Signed-off-by: Jakub Palider <jpa@semihalf.com>
2016-03-17 14:31:15 +00:00
Amazon ENA
maintainers: update for ena Following changes of the ENA driver ownership in Amazon and Semihalf (Jakub and Jan no longer work in the company), update driver's maintainers list. Special thanks to Jan Medala and Jakub Palider for their support and development. Signed-off-by: Marcin Wojtas <mw@semihalf.com> Acked-by: Jan Medala <jan.medala@outlook.com>
2017-04-12 14:21:49 +00:00
M: Marcin Wojtas <mw@semihalf.com>
M: Michal Krawczyk <mk@semihalf.com>
M: Guy Tzalik <gtzalik@amazon.com>
ena: introduce documentation Signed-off-by: Alexander Matushevsky <matua@amazon.com> Signed-off-by: Jan Medala <jan@semihalf.com> Signed-off-by: Jakub Palider <jpa@semihalf.com>
2016-03-17 14:31:15 +00:00
M: Evgeny Schemeilin <evgenys@amazon.com>
maintainers: update for ena Add Igor Chauskin from the Amazon as another maintainer of the driver. Igor is another person from the Amazon team that is responsible for the ENA DPDK driver. Signed-off-by: Michal Krawczyk <mk@semihalf.com>
2019-09-26 10:45:27 +00:00
M: Igor Chauskin <igorch@amazon.com>
ena: introduce documentation Signed-off-by: Alexander Matushevsky <matua@amazon.com> Signed-off-by: Jan Medala <jan@semihalf.com> Signed-off-by: Jakub Palider <jpa@semihalf.com>
2016-03-17 14:31:15 +00:00
F: drivers/net/ena/
F: doc/guides/nics/ena.rst
maintainers: add drivers features files Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-05-10 13:33:50 +00:00
F: doc/guides/nics/features/ena.ini
ena: introduce documentation Signed-off-by: Alexander Matushevsky <matua@amazon.com> Signed-off-by: Jan Medala <jan@semihalf.com> Signed-off-by: Jakub Palider <jpa@semihalf.com>
2016-03-17 14:31:15 +00:00
maintainers: fix typo and ordering Fix logical/alphabetical ordering, spacing, and syntax typo. Fixes: 8fb3b2576025 ("maintainers: call out subtree committers") Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2018-04-23 01:18:35 +00:00
AMD axgbe
maintainers: update for AMD axgbe and CCP crypto Ownership change. Signed-off-by: Amaranath Somalapuram <asomalap@amd.com> Acked-by: Ravi Kumar <ravi1.kumar@amd.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
2020-04-27 06:11:45 +00:00
M: Somalapuram Amaranath <asomalap@amd.com>
maintainers: fix typo and ordering Fix logical/alphabetical ordering, spacing, and syntax typo. Fixes: 8fb3b2576025 ("maintainers: call out subtree committers") Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2018-04-23 01:18:35 +00:00
F: drivers/net/axgbe/
F: doc/guides/nics/axgbe.rst
F: doc/guides/nics/features/axgbe.ini
net/atlantic: add PMD driver skeleton Makefile/meson build infrastructure, atl_ethdev minimal skeleton, header with aquantia aQtion NIC device and vendor IDs. Signed-off-by: Igor Russkikh <igor.russkikh@aquantia.com> Signed-off-by: Pavel Belous <pavel.belous@aquantia.com>
2018-10-12 11:09:03 +00:00
Aquantia atlantic
M: Igor Russkikh <igor.russkikh@aquantia.com>
M: Pavel Belous <pavel.belous@aquantia.com>
F: drivers/net/atlantic/
F: doc/guides/nics/atlantic.rst
F: doc/guides/nics/features/atlantic.ini
net/ark: stub PMD for Atomic Rules Arkville Enable Arkville on supported configurations Add overview documentation Minimum driver support for valid compile Arkville PMD is not supported on ARM or PowerPC at this time Signed-off-by: Ed Czeck <ed.czeck@atomicrules.com> Signed-off-by: John Miller <john.miller@atomicrules.com>
2017-04-04 19:50:23 +00:00
Atomic Rules ARK
M: Shepard Siegel <shepard.siegel@atomicrules.com>
M: Ed Czeck <ed.czeck@atomicrules.com>
M: John Miller <john.miller@atomicrules.com>
F: drivers/net/ark/
F: doc/guides/nics/ark.rst
F: doc/guides/nics/features/ark.ini
net/bnxt: add driver for Broadcom NetXtreme-C devices This patch adds the initial skeleton for bnxt driver along with the nic guide, and ties the driver into the build system. At this point, the driver simply fails init. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Signed-off-by: Stephen Hurd <stephen.hurd@broadcom.com> Reviewed-by: David Christensen <david.christensen@broadcom.com> [Release Note Addition] Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2016-06-15 21:23:01 +00:00
Broadcom bnxt
maintainers: add new bnxt driver maintainer Add Ajit Khaparde as the maintainer of the bnxt PMD Reviewed-by: David Christensen <david.christensen@broadcom.com> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Acked-by: Stephen Hurd <stephen.hurd@broadcom.com>
2016-09-21 22:27:14 +00:00
M: Ajit Khaparde <ajit.khaparde@broadcom.com>
maintainers: update for bnxt Remove Stephen Hurd and add Somnath Kotur to maintain bnxt PMD. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
2017-12-14 17:53:33 +00:00
M: Somnath Kotur <somnath.kotur@broadcom.com>
maintainers: add next-net-brcm sub-tree Adding vendor specific sub-tree for Broadcom drivers. The next-net-brcm sub-tree will be sub-tree of the next-net. Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2019-10-15 07:38:00 +00:00
T: git://dpdk.org/next/dpdk-next-net-brcm
net/bnxt: add driver for Broadcom NetXtreme-C devices This patch adds the initial skeleton for bnxt driver along with the nic guide, and ties the driver into the build system. At this point, the driver simply fails init. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Signed-off-by: Stephen Hurd <stephen.hurd@broadcom.com> Reviewed-by: David Christensen <david.christensen@broadcom.com> [Release Note Addition] Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2016-06-15 21:23:01 +00:00
F: drivers/net/bnxt/
F: doc/guides/nics/bnxt.rst
maintainers: add drivers features files Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-05-10 13:33:50 +00:00
F: doc/guides/nics/features/bnxt.ini
net/bnxt: add driver for Broadcom NetXtreme-C devices This patch adds the initial skeleton for bnxt driver along with the nic guide, and ties the driver into the build system. At this point, the driver simply fails init. Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com> Signed-off-by: Stephen Hurd <stephen.hurd@broadcom.com> Reviewed-by: David Christensen <david.christensen@broadcom.com> [Release Note Addition] Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2016-06-15 21:23:01 +00:00
doc: add ThunderX nicvf Updated doc/guides/nics/overview.rst, doc/guides/nics/thunderx.rst and release notes Changed "*" to "P" in overview.rst to capture the partially supported feature as "*" creating alignment issues with Sphinx table Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Signed-off-by: Slawomir Rosek <slawomir.rosek@semihalf.com> Signed-off-by: Maciej Czekaj <maciej.czekaj@caviumnetworks.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-06-17 13:29:53 +00:00
Cavium ThunderX nicvf
maintainers: update Cavium email ids Following Marvell's acquisition of Cavium, we need to update all the Cavium maintainer's entries to point to our new e-mail addresses. Update maintainers as they are no longer working for Cavium. Thanks to Harish Patil for his support and development of our various dpdk drivers. Signed-off-by: Jerin Jacob <jerinj@marvell.com>
2018-12-16 15:43:25 +00:00
M: Jerin Jacob <jerinj@marvell.com>
M: Maciej Czekaj <mczekaj@marvell.com>
maintainers: claim maintainership of net-mrvl sub-tree Claim the maintainership of the sub tree dpdk-next-net-mrvl, which covers all the Marvell network PMDs. Signed-off-by: Jerin Jacob <jerinj@marvell.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2019-06-25 05:42:41 +00:00
T: git://dpdk.org/next/dpdk-next-net-mrvl
doc: add ThunderX nicvf Updated doc/guides/nics/overview.rst, doc/guides/nics/thunderx.rst and release notes Changed "*" to "P" in overview.rst to capture the partially supported feature as "*" creating alignment issues with Sphinx table Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Signed-off-by: Slawomir Rosek <slawomir.rosek@semihalf.com> Signed-off-by: Maciej Czekaj <maciej.czekaj@caviumnetworks.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-06-17 13:29:53 +00:00
F: drivers/net/thunderx/
F: doc/guides/nics/thunderx.rst
maintainers: add drivers features files Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-05-10 13:33:50 +00:00
F: doc/guides/nics/features/thunderx.ini
doc: add ThunderX nicvf Updated doc/guides/nics/overview.rst, doc/guides/nics/thunderx.rst and release notes Changed "*" to "P" in overview.rst to capture the partially supported feature as "*" creating alignment issues with Sphinx table Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Signed-off-by: Slawomir Rosek <slawomir.rosek@semihalf.com> Signed-off-by: Maciej Czekaj <maciej.czekaj@caviumnetworks.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-06-17 13:29:53 +00:00
net/liquidio: add skeleton Add makefile and config file options to compile PMD. Add feature and version map file. Update maintainers file to claim responsibility. Signed-off-by: Shijith Thotton <shijith.thotton@caviumnetworks.com> Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Signed-off-by: Derek Chickles <derek.chickles@caviumnetworks.com> Signed-off-by: Venkat Koppula <venkat.koppula@caviumnetworks.com> Signed-off-by: Srisivasubramanian S <ssrinivasan@caviumnetworks.com> Signed-off-by: Mallesham Jatharakonda <mjatharakonda@oneconvergence.com>
2017-03-25 06:24:12 +00:00
Cavium LiquidIO
maintainers: update Cavium email ids Following Marvell's acquisition of Cavium, we need to update all the Cavium maintainer's entries to point to our new e-mail addresses. Update maintainers as they are no longer working for Cavium. Thanks to Harish Patil for his support and development of our various dpdk drivers. Signed-off-by: Jerin Jacob <jerinj@marvell.com>
2018-12-16 15:43:25 +00:00
M: Shijith Thotton <sthotton@marvell.com>
M: Srisivasubramanian Srinivasan <srinivasan@marvell.com>
maintainers: claim maintainership of net-mrvl sub-tree Claim the maintainership of the sub tree dpdk-next-net-mrvl, which covers all the Marvell network PMDs. Signed-off-by: Jerin Jacob <jerinj@marvell.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2019-06-25 05:42:41 +00:00
T: git://dpdk.org/next/dpdk-next-net-mrvl
net/liquidio: add skeleton Add makefile and config file options to compile PMD. Add feature and version map file. Update maintainers file to claim responsibility. Signed-off-by: Shijith Thotton <shijith.thotton@caviumnetworks.com> Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Signed-off-by: Derek Chickles <derek.chickles@caviumnetworks.com> Signed-off-by: Venkat Koppula <venkat.koppula@caviumnetworks.com> Signed-off-by: Srisivasubramanian S <ssrinivasan@caviumnetworks.com> Signed-off-by: Mallesham Jatharakonda <mjatharakonda@oneconvergence.com>
2017-03-25 06:24:12 +00:00
F: drivers/net/liquidio/
doc: add liquidio Add liquidio driver documentation and update 17.05 release notes. Signed-off-by: Shijith Thotton <shijith.thotton@caviumnetworks.com> Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Signed-off-by: Derek Chickles <derek.chickles@caviumnetworks.com> Signed-off-by: Venkat Koppula <venkat.koppula@caviumnetworks.com> Signed-off-by: Srisivasubramanian S <ssrinivasan@caviumnetworks.com> Signed-off-by: Mallesham Jatharakonda <mjatharakonda@oneconvergence.com>
2017-03-25 06:24:57 +00:00
F: doc/guides/nics/liquidio.rst
net/liquidio: add skeleton Add makefile and config file options to compile PMD. Add feature and version map file. Update maintainers file to claim responsibility. Signed-off-by: Shijith Thotton <shijith.thotton@caviumnetworks.com> Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Signed-off-by: Derek Chickles <derek.chickles@caviumnetworks.com> Signed-off-by: Venkat Koppula <venkat.koppula@caviumnetworks.com> Signed-off-by: Srisivasubramanian S <ssrinivasan@caviumnetworks.com> Signed-off-by: Mallesham Jatharakonda <mjatharakonda@oneconvergence.com>
2017-03-25 06:24:12 +00:00
F: doc/guides/nics/features/liquidio.ini
use registered name for OCTEON TX references 'OCTEON TX' is the registered name. All other usages need to be fixed. Signed-off-by: Anoob Joseph <anoob.joseph@caviumnetworks.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2018-10-10 02:50:56 +00:00
Cavium OCTEON TX
maintainers: update for OCTEON TX Harman thankfully accepted to replace myself as maintainer for OCTEONTX ethdev PMD. Signed-off-by: Jerin Jacob <jerinj@marvell.com> Acked-by: Harman Kalra <hkalra@marvell.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
2019-12-11 14:23:42 +00:00
M: Harman Kalra <hkalra@marvell.com>
maintainers: claim maintainership of net-mrvl sub-tree Claim the maintainership of the sub tree dpdk-next-net-mrvl, which covers all the Marvell network PMDs. Signed-off-by: Jerin Jacob <jerinj@marvell.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2019-06-25 05:42:41 +00:00
T: git://dpdk.org/next/dpdk-next-net-mrvl
common/octeontx: move mbox to common folder Move commonly used functions across mempool, event and net devices to a common folder in drivers. Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Acked-by: Santosh Shukla <santosh.shukla@caviumnetworks.com>
2018-04-04 14:30:25 +00:00
F: drivers/common/octeontx/
mempool/octeontx: add HW constants add HW constants of octeontx fpa mempool device. Signed-off-by: Santosh Shukla <santosh.shukla@caviumnetworks.com> Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2017-10-08 12:40:02 +00:00
F: drivers/mempool/octeontx/
net/octeontx: add build infrastructure Adding bare minimum PMD library and doc build infrastructure. Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Signed-off-by: Santosh Shukla <santosh.shukla@caviumnetworks.com>
2017-10-08 12:44:05 +00:00
F: drivers/net/octeontx/
doc: add octeontx ethdev driver documentation Adding octeontx ethdev driver documentation and claim octeontx ethdev driver maintainership. Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Signed-off-by: Santosh Shukla <santosh.shukla@caviumnetworks.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2017-10-08 12:44:30 +00:00
F: doc/guides/nics/octeontx.rst
net/octeontx: add build infrastructure Adding bare minimum PMD library and doc build infrastructure. Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Signed-off-by: Santosh Shukla <santosh.shukla@caviumnetworks.com>
2017-10-08 12:44:05 +00:00
F: doc/guides/nics/features/octeontx.ini
mempool/octeontx: add HW constants add HW constants of octeontx fpa mempool device. Signed-off-by: Santosh Shukla <santosh.shukla@caviumnetworks.com> Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2017-10-08 12:40:02 +00:00
cxgbe: add pmd skeleton Adds cxgbe poll mode driver for DPDK under drivers/net/cxgbe directory. This patch: 1. Adds the Makefile to compile cxgbe pmd. 2. Registers and initializes the cxgbe pmd driver. Enable cxgbe PMD for compilation and linking with changes to: 1. config/common_linuxapp to add macros for cxgbe pmd. 2. drivers/net/Makefile to add cxgbe pmd to the compile list. 3. mk/rte.app.mk to add cxgbe pmd to link. Update MAINTAINERS file to claim responsibility for the cxgbe PMD. Signed-off-by: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com> Signed-off-by: Kumar Sanghvi <kumaras@chelsio.com> [Thomas: add disabled config for bsdapp]
2015-06-29 23:28:35 +00:00
Chelsio cxgbe
M: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
F: drivers/net/cxgbe/
cxgbe: add documentation Adds cxgbe poll mode driver documentation under the usual doc/guides/nics/ directory with the rest of the drivers. The documentation covers cxgbe implementation details, features and limitations, prerequisites, configuration, and a sample application usage. Signed-off-by: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com> Signed-off-by: Kumar Sanghvi <kumaras@chelsio.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2015-06-29 23:28:42 +00:00
F: doc/guides/nics/cxgbe.rst
maintainers: add drivers features files Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-05-10 13:33:50 +00:00
F: doc/guides/nics/features/cxgbe.ini
cxgbe: add pmd skeleton Adds cxgbe poll mode driver for DPDK under drivers/net/cxgbe directory. This patch: 1. Adds the Makefile to compile cxgbe pmd. 2. Registers and initializes the cxgbe pmd driver. Enable cxgbe PMD for compilation and linking with changes to: 1. config/common_linuxapp to add macros for cxgbe pmd. 2. drivers/net/Makefile to add cxgbe pmd to the compile list. 3. mk/rte.app.mk to add cxgbe pmd to link. Update MAINTAINERS file to claim responsibility for the cxgbe PMD. Signed-off-by: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com> Signed-off-by: Kumar Sanghvi <kumaras@chelsio.com> [Thomas: add disabled config for bsdapp]
2015-06-29 23:28:35 +00:00
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
Cisco enic
maintainers: add maintainers for enic Signed-off-by: John Daley <johndale@cisco.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-11-05 19:14:25 +00:00
M: John Daley <johndale@cisco.com>
maintainers: update for enic Welcome Hyong Youb Kim. Signed-off-by: John Daley <johndale@cisco.com>
2018-01-10 09:17:01 +00:00
M: Hyong Youb Kim <hyonkim@cisco.com>
enic: move to drivers/net/ move enic PMD to drivers/net directory Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: John McNamara <john.mcnamara@intel.com> [Thomas: move vnic/ to base/] Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-05-15 15:56:50 +00:00
F: drivers/net/enic/
enic: update maintainers Change maintainers for ENIC PMD and fix pointer to enic documentation in MAINTAINERS. Signed-off-by: John Daley <johndale@cisco.com>
2016-03-18 18:27:07 +00:00
F: doc/guides/nics/enic.rst
maintainers: add drivers features files Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-05-10 13:33:50 +00:00
F: doc/guides/nics/features/enic.ini
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
net/hns3: add build and doc infrastructure This patch adds build and doc infrastructure for hns3 PMD driver. Signed-off-by: Wei Hu (Xavier) <xavier.huwei@huawei.com> Signed-off-by: Min Hu (Connor) <humin29@huawei.com> Signed-off-by: Chunsong Feng <fengchunsong@huawei.com> Signed-off-by: Hao Chen <chenhao164@huawei.com> Signed-off-by: Huisong Li <lihuisong@huawei.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
2019-09-26 14:01:47 +00:00
Hisilicon hns3
M: Wei Hu (Xavier) <xavier.huwei@huawei.com>
M: Min Hu (Connor) <humin29@huawei.com>
M: Yisen Zhuang <yisen.zhuang@huawei.com>
F: drivers/net/hns3/
F: doc/guides/nics/hns3.rst
F: doc/guides/nics/features/hns3.ini
net/hinic: add build and doc files Add build and doc files along with hinic_pmd_ethdev.c which just includes PMD register and log initialization for compilation. Signed-off-by: Ziyang Xuan <xuanziyang2@huawei.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
2019-06-27 08:18:20 +00:00
Huawei hinic
M: Ziyang Xuan <xuanziyang2@huawei.com>
M: Xiaoyun Wang <cloud.wangxiaoyun@huawei.com>
M: Guoyang Zhou <zhouguoyang@huawei.com>
F: drivers/net/hinic/
F: doc/guides/nics/hinic.rst
F: doc/guides/nics/features/hinic.ini
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
Intel e1000
maintainers: update for Intel ixgbe/igb/igc Replace Wenzhuo Lu, Alvin Zhang and Konstantin Ananyev with Wei Zhao and Jeff Guo. Signed-off-by: Wei Zhao <wei.zhao1@intel.com> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Wenzhuo Lu <wenzhuo.lu@intel.com> Acked-by: Jeff Guo <jia.guo@intel.com> Acked-by: Alvin Zhang <alvinx.zhang@intel.com>
2020-04-27 01:28:59 +00:00
M: Wei Zhao <wei.zhao1@intel.com>
M: Jeff Guo <jia.guo@intel.com>
maintainers: claim maintainership of net-intel sub tree Claim the maintainership of the sub tree dpdk-next-net-intel, which covers all the Intel PMDs. Signed-off-by: Helin Zhang <helin.zhang@intel.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2018-01-09 13:50:07 +00:00
T: git://dpdk.org/next/dpdk-next-net-intel
e1000: move to drivers/net/ Move e1000 pmd to drivers/net directory As part of move, rename "e1000" subdirectory, which contains the code from the "base driver", to "base". Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: John McNamara <john.mcnamara@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-05-15 15:56:49 +00:00
F: drivers/net/e1000/
doc: nics guide Create nics guide by moving chapters about Intel and Mellanox NICs. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Siobhan Butler <siobhan.a.butler@intel.com>
2015-01-31 22:06:06 +00:00
F: doc/guides/nics/e1000em.rst
F: doc/guides/nics/intel_vf.rst
maintainers: add drivers features files Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-05-10 13:33:50 +00:00
F: doc/guides/nics/features/e1000.ini
F: doc/guides/nics/features/igb*.ini
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
Intel ixgbe
maintainers: update for Intel ixgbe/igb/igc Replace Wenzhuo Lu, Alvin Zhang and Konstantin Ananyev with Wei Zhao and Jeff Guo. Signed-off-by: Wei Zhao <wei.zhao1@intel.com> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Wenzhuo Lu <wenzhuo.lu@intel.com> Acked-by: Jeff Guo <jia.guo@intel.com> Acked-by: Alvin Zhang <alvinx.zhang@intel.com>
2020-04-27 01:28:59 +00:00
M: Wei Zhao <wei.zhao1@intel.com>
M: Jeff Guo <jia.guo@intel.com>
maintainers: claim maintainership of net-intel sub tree Claim the maintainership of the sub tree dpdk-next-net-intel, which covers all the Intel PMDs. Signed-off-by: Helin Zhang <helin.zhang@intel.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2018-01-09 13:50:07 +00:00
T: git://dpdk.org/next/dpdk-next-net-intel
ixgbe: move to drivers/net/ move ixgbe PMD to drivers/net directory. As part of the move, we rename the ixgbe directory, containing the ixgbe "base driver" code, from "ixgbe" to "base". Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: John McNamara <john.mcnamara@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-05-15 15:56:53 +00:00
F: drivers/net/ixgbe/
doc: nics guide Create nics guide by moving chapters about Intel and Mellanox NICs. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Siobhan Butler <siobhan.a.butler@intel.com>
2015-01-31 22:06:06 +00:00
F: doc/guides/nics/ixgbe.rst
F: doc/guides/nics/intel_vf.rst
maintainers: add drivers features files Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-05-10 13:33:50 +00:00
F: doc/guides/nics/features/ixgbe*.ini
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
Intel i40e
maintainers: update for i40e Signed-off-by: Beilei Xing <beilei.xing@intel.com> Acked-by: Helin Zhang <helin.zhang@intel.com>
2017-06-29 01:11:38 +00:00
M: Beilei Xing <beilei.xing@intel.com>
maintainers: update for Intel i40e Replace Qi Zhang with Jeff Guo. Signed-off-by: Beilei Xing <beilei.xing@intel.com> Acked-by: Jeff Guo <jia.guo@intel.com> Acked-by: Qi Zhang <qi.z.zhang@intel.com>
2020-04-26 08:21:51 +00:00
M: Jeff Guo <jia.guo@intel.com>
maintainers: claim maintainership of net-intel sub tree Claim the maintainership of the sub tree dpdk-next-net-intel, which covers all the Intel PMDs. Signed-off-by: Helin Zhang <helin.zhang@intel.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2018-01-09 13:50:07 +00:00
T: git://dpdk.org/next/dpdk-next-net-intel
i40e: move to drivers/net/ Move i40e PMD to drivers/net directory. As part of the move, rename the "i40e" directory, containing the "base driver" code, from "i40e" to "base". Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: John McNamara <john.mcnamara@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-05-18 11:05:12 +00:00
F: drivers/net/i40e/
maintainers: claim responsibility for Intel i40e driver Signed-off-by: Jingjing Wu <jingjing.wu@intel.com> Acked-by: Helin Zhang <helin.zhang@intel.com>
2016-03-29 03:21:56 +00:00
F: doc/guides/nics/i40e.rst
doc: nics guide Create nics guide by moving chapters about Intel and Mellanox NICs. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Siobhan Butler <siobhan.a.butler@intel.com>
2015-01-31 22:06:06 +00:00
F: doc/guides/nics/intel_vf.rst
maintainers: add drivers features files Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-05-10 13:33:50 +00:00
F: doc/guides/nics/features/i40e*.ini
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
maintainers: claim for fm10k review Claim for fm10k polling mode driver review. Signed-off-by: Chen Jing D(Mark) <jing.d.chen@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-02-12 10:06:07 +00:00
Intel fm10k
maintainers: update for fm10k Signed-off-by: Xiao Wang <xiao.w.wang@intel.com> Acked-by: Helin Zhang <helin.zhang@intel.com>
2017-10-25 11:22:54 +00:00
M: Qi Zhang <qi.z.zhang@intel.com>
M: Xiao Wang <xiao.w.wang@intel.com>
maintainers: claim maintainership of net-intel sub tree Claim the maintainership of the sub tree dpdk-next-net-intel, which covers all the Intel PMDs. Signed-off-by: Helin Zhang <helin.zhang@intel.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2018-01-09 13:50:07 +00:00
T: git://dpdk.org/next/dpdk-next-net-intel
fm10k: move to drivers/net/ move fm10k PMD to drivers/net directory Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: John McNamara <john.mcnamara@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-05-15 15:56:51 +00:00
F: drivers/net/fm10k/
maintainers: add missing doc references Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-05-22 14:28:30 +00:00
F: doc/guides/nics/fm10k.rst
maintainers: add drivers features files Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-05-10 13:33:50 +00:00
F: doc/guides/nics/features/fm10k*.ini
maintainers: claim for fm10k review Claim for fm10k polling mode driver review. Signed-off-by: Chen Jing D(Mark) <jing.d.chen@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-02-12 10:06:07 +00:00
net/iavf: rename avf to iavf Rename Intel Ethernet Adaptive Virtual Function driver avf to iavf. This is the first patch which will only renames the directory name, lib name, filenames and updates the new name in makefile and meson files. Also updates the #include files in source files. Signed-off-by: Leyi Rong <leyi.rong@intel.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
2019-02-25 17:18:51 +00:00
Intel iavf
net/avf/base: add base code for avf PMD Signed-off-by: Jingjing Wu <jingjing.wu@intel.com> Signed-off-by: Wenzhuo Lu <wenzhuo.lu@intel.com>
2018-01-10 13:01:53 +00:00
M: Jingjing Wu <jingjing.wu@intel.com>
maintainers: update for Intel iavf Replace Wenzhuo Lu with Beilei Xing. Signed-off-by: Beilei Xing <beilei.xing@intel.com> Acked-by: Wenzhuo Lu <wenzhuo.lu@intel.com>
2020-04-26 08:21:52 +00:00
M: Beilei Xing <beilei.xing@intel.com>
maintainers: maintain avf PMD in next-net-intel Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-04-04 15:13:03 +00:00
T: git://dpdk.org/next/dpdk-next-net-intel
net/iavf: rename avf to iavf Rename Intel Ethernet Adaptive Virtual Function driver avf to iavf. This is the first patch which will only renames the directory name, lib name, filenames and updates the new name in makefile and meson files. Also updates the #include files in source files. Signed-off-by: Leyi Rong <leyi.rong@intel.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
2019-02-25 17:18:51 +00:00
F: drivers/net/iavf/
net/iavf/base: move to drivers common directory Change the iavf base code as driver common library, it is used by iavf PMD now, and it can be used by other Intel SR-IOV PMDs in the future. Signed-off-by: Haiyue Wang <haiyue.wang@intel.com> Acked-by: Qi Zhang <qi.z.zhang@intel.com>
2020-01-10 01:37:49 +00:00
F: drivers/common/iavf/
net/iavf: rename avf to iavf Rename Intel Ethernet Adaptive Virtual Function driver avf to iavf. This is the first patch which will only renames the directory name, lib name, filenames and updates the new name in makefile and meson files. Also updates the #include files in source files. Signed-off-by: Leyi Rong <leyi.rong@intel.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
2019-02-25 17:18:51 +00:00
F: doc/guides/nics/features/iavf*.ini
net/avf/base: add base code for avf PMD Signed-off-by: Jingjing Wu <jingjing.wu@intel.com> Signed-off-by: Wenzhuo Lu <wenzhuo.lu@intel.com>
2018-01-10 13:01:53 +00:00
net/ice/base: add registers for Intel E800 Series NIC Add the registers that comprise the Intel(R) 800 Series NIC. There is no functionality in this patch. Signed-off-by: Paul M Stillwell Jr <paul.m.stillwell.jr@intel.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-12-18 08:46:10 +00:00
Intel ice
M: Qiming Yang <qiming.yang@intel.com>
maintainers: update for ice Replace Wenzhuo Lu with Qi Zhang. Signed-off-by: Qi Zhang <qi.z.zhang@intel.com> Acked-by: Wenzhuo Lu <wenzhuo.lu@intel.com>
2020-04-30 09:28:05 +00:00
M: Qi Zhang <qi.z.zhang@intel.com>
net/ice/base: add registers for Intel E800 Series NIC Add the registers that comprise the Intel(R) 800 Series NIC. There is no functionality in this patch. Signed-off-by: Paul M Stillwell Jr <paul.m.stillwell.jr@intel.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-12-18 08:46:10 +00:00
T: git://dpdk.org/next/dpdk-next-net-intel
F: drivers/net/ice/
net/ice: support device initialization Update the documents too. Signed-off-by: Wenzhuo Lu <wenzhuo.lu@intel.com> Signed-off-by: Qiming Yang <qiming.yang@intel.com> Signed-off-by: Xiaoyun Li <xiaoyun.li@intel.com> Signed-off-by: Jingjing Wu <jingjing.wu@intel.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com> Reviewed-by: Qi Zhang <qi.z.zhang@intel.com>
2018-12-18 08:46:24 +00:00
F: doc/guides/nics/ice.rst
F: doc/guides/nics/features/ice.ini
net/ice/base: add registers for Intel E800 Series NIC Add the registers that comprise the Intel(R) 800 Series NIC. There is no functionality in this patch. Signed-off-by: Paul M Stillwell Jr <paul.m.stillwell.jr@intel.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-12-18 08:46:10 +00:00
net/igc: add skeleton Implement device detection and loading. Add igc driver guide docs. Signed-off-by: Alvin Zhang <alvinx.zhang@intel.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
2020-04-15 08:48:00 +00:00
Intel igc
maintainers: update for Intel ixgbe/igb/igc Replace Wenzhuo Lu, Alvin Zhang and Konstantin Ananyev with Wei Zhao and Jeff Guo. Signed-off-by: Wei Zhao <wei.zhao1@intel.com> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Wenzhuo Lu <wenzhuo.lu@intel.com> Acked-by: Jeff Guo <jia.guo@intel.com> Acked-by: Alvin Zhang <alvinx.zhang@intel.com>
2020-04-27 01:28:59 +00:00
M: Wei Zhao <wei.zhao1@intel.com>
M: Jeff Guo <jia.guo@intel.com>
net/igc: add skeleton Implement device detection and loading. Add igc driver guide docs. Signed-off-by: Alvin Zhang <alvinx.zhang@intel.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
2020-04-15 08:48:00 +00:00
T: git://dpdk.org/next/dpdk-next-net-intel
F: drivers/net/igc/
F: doc/guides/nics/igc.rst
F: doc/guides/nics/features/igc.ini
net/ipn3ke: add new driver Add Intel FPGA Acceleration NIC IPN3KE ethdev PMD driver. Signed-off-by: Rosen Xu <rosen.xu@intel.com> Signed-off-by: Andy Pei <andy.pei@intel.com> Signed-off-by: Dan Wei <dan.wei@intel.com>
2019-04-16 03:17:40 +00:00
Intel ipn3ke
M: Rosen Xu <rosen.xu@intel.com>
T: git://dpdk.org/next/dpdk-next-net-intel
F: drivers/net/ipn3ke/
F: doc/guides/nics/ipn3ke.rst
F: doc/guides/nics/features/ipn3ke.ini
maintainers: fix typo and ordering Fix logical/alphabetical ordering, spacing, and syntax typo. Fixes: 8fb3b2576025 ("maintainers: call out subtree committers") Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2018-04-23 01:18:35 +00:00
Marvell mvpp2
maintainers: update Marvell PMDs Natalie and Dmitri are no longer involved in PMDs maintenance hence update the list. Also append new active maintainers to the list. Signed-off-by: Liron Himi <lironh@marvell.com> Acked-by: Tomasz Duszynski <tdu@semihalf.com>
2019-02-20 15:01:59 +00:00
M: Liron Himi <lironh@marvell.com>
maintainers: claim maintainership of net-mrvl sub-tree Claim the maintainership of the sub tree dpdk-next-net-mrvl, which covers all the Marvell network PMDs. Signed-off-by: Jerin Jacob <jerinj@marvell.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2019-06-25 05:42:41 +00:00
T: git://dpdk.org/next/dpdk-next-net-mrvl
common/mvep: add common code for Marvell drivers Add MVEP (Marvell Embedded Processors) to drivers/common which will keep code reused by current and future MRVL PMDs. Right now we have only common DMA memory initialization routines there. Signed-off-by: Liron Himi <lironh@marvell.com> Signed-off-by: Tomasz Duszynski <tdu@semihalf.com> Reviewed-by: Natalie Samsonov <nsamsono@marvell.com>
2018-08-24 18:29:58 +00:00
F: drivers/common/mvep/
maintainers: fix typo and ordering Fix logical/alphabetical ordering, spacing, and syntax typo. Fixes: 8fb3b2576025 ("maintainers: call out subtree committers") Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2018-04-23 01:18:35 +00:00
F: drivers/net/mvpp2/
F: doc/guides/nics/mvpp2.rst
F: doc/guides/nics/features/mvpp2.ini
net/mvneta: add PMD skeleton Add neta pmd driver skeleton providing base for the further development. Signed-off-by: Natalie Samsonov <nsamsono@marvell.com> Signed-off-by: Yelena Krivosheev <yelena@marvell.com> Signed-off-by: Dmitri Epshtein <dima@marvell.com> Signed-off-by: Zyta Szpak <zr@semihalf.com> Signed-off-by: Andrzej Ostruszka <amo@semihalf.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-10-03 07:22:09 +00:00
Marvell mvneta
M: Zyta Szpak <zr@semihalf.com>
maintainers: update Marvell PMDs Natalie and Dmitri are no longer involved in PMDs maintenance hence update the list. Also append new active maintainers to the list. Signed-off-by: Liron Himi <lironh@marvell.com> Acked-by: Tomasz Duszynski <tdu@semihalf.com>
2019-02-20 15:01:59 +00:00
M: Liron Himi <lironh@marvell.com>
maintainers: claim maintainership of net-mrvl sub-tree Claim the maintainership of the sub tree dpdk-next-net-mrvl, which covers all the Marvell network PMDs. Signed-off-by: Jerin Jacob <jerinj@marvell.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2019-06-25 05:42:41 +00:00
T: git://dpdk.org/next/dpdk-next-net-mrvl
net/mvneta: add PMD skeleton Add neta pmd driver skeleton providing base for the further development. Signed-off-by: Natalie Samsonov <nsamsono@marvell.com> Signed-off-by: Yelena Krivosheev <yelena@marvell.com> Signed-off-by: Dmitri Epshtein <dima@marvell.com> Signed-off-by: Zyta Szpak <zr@semihalf.com> Signed-off-by: Andrzej Ostruszka <amo@semihalf.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-10-03 07:22:09 +00:00
F: drivers/net/mvneta/
F: doc/guides/nics/mvneta.rst
F: doc/guides/nics/features/mvneta.ini
net/octeontx2: add build and doc infrastructure Adding bare minimum PMD library and doc build infrastructure and claim the maintainership for octeontx2 PMD. Signed-off-by: Jerin Jacob <jerinj@marvell.com> Signed-off-by: Nithin Dabilpuram <ndabilpuram@marvell.com> Signed-off-by: Kiran Kumar K <kirankumark@marvell.com>
2019-05-28 08:55:22 +00:00
Marvell OCTEON TX2
M: Jerin Jacob <jerinj@marvell.com>
M: Nithin Dabilpuram <ndabilpuram@marvell.com>
M: Kiran Kumar K <kirankumark@marvell.com>
T: git://dpdk.org/next/dpdk-next-net-mrvl
F: drivers/net/octeontx2/
F: doc/guides/nics/features/octeontx2*.ini
F: doc/guides/nics/octeontx2.rst
common/octeontx2: add security capability routine This routine returns true if given rte_eth_dev is security offload capable and belongs to octeontx2. Signed-off-by: Anoob Joseph <anoobj@marvell.com> Signed-off-by: Tejasree Kondoj <ktejasree@marvell.com> Signed-off-by: Vamsi Attunuru <vattunuru@marvell.com> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
2020-02-04 11:17:12 +00:00
Marvell OCTEON TX2 - security
M: Anoob Joseph <anoobj@marvell.com>
T: git://dpdk.org/next/dpdk-next-crypto
F: drivers/common/octeontx2/otx2_sec*
net/octeontx2: create security context Adding security ctx to the eth device. Signed-off-by: Ankur Dwivedi <adwivedi@marvell.com> Signed-off-by: Anoob Joseph <anoobj@marvell.com> Signed-off-by: Archana Muniganti <marchana@marvell.com> Signed-off-by: Tejasree Kondoj <ktejasree@marvell.com> Signed-off-by: Vamsi Attunuru <vattunuru@marvell.com> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
2020-02-04 11:17:14 +00:00
F: drivers/net/octeontx2/otx2_ethdev_sec*
common/octeontx2: add security capability routine This routine returns true if given rte_eth_dev is security offload capable and belongs to octeontx2. Signed-off-by: Anoob Joseph <anoobj@marvell.com> Signed-off-by: Tejasree Kondoj <ktejasree@marvell.com> Signed-off-by: Vamsi Attunuru <vattunuru@marvell.com> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
2020-02-04 11:17:12 +00:00
mlx4: new poll mode driver This PMD manages all variants of Mellanox ConnectX-3 (EN 40, EN 10, Pro EN 40) as well as their virtual functions in SR-IOV context through IB Verbs (libibverbs) and the dedicated user-space driver (libmlx4). It is disabled by default due to dependencies on these libraries and only supports Linux userland at the moment partly because /sys (sysfs) support is required. Also claim responsibility in the MAINTAINERS file. Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com> Signed-off-by: Olga Shern <olgas@mellanox.com>
2015-02-25 13:52:05 +00:00
Mellanox mlx4
maintainers: update for Mellanox PMDs Shahaf and Matan volunteered to replace Nélio and myself as maintainers for mlx4 and mlx5 PMDs. Cheers! Cc: stable@dpdk.org Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com> Signed-off-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com> Acked-by: Shahaf Shuler <shahafs@mellanox.com> Acked-by: Matan Azrad <matan@mellanox.com> Acked-by: Yongseok Koh <yskoh@mellanox.com>
2018-07-05 09:19:46 +00:00
M: Matan Azrad <matan@mellanox.com>
M: Shahaf Shuler <shahafs@mellanox.com>
maintainers: update mlx drivers sub tree Mellanox PMD patches should target the next-net-mlx sub tree. Signed-off-by: Shahaf Shuler <shahafs@mellanox.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2018-01-04 20:01:07 +00:00
T: git://dpdk.org/next/dpdk-next-net-mlx
mlx4: move to drivers/net/ move mlx4 PMD to drivers/net directory Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: John McNamara <john.mcnamara@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-05-15 15:56:54 +00:00
F: drivers/net/mlx4/
doc: nics guide Create nics guide by moving chapters about Intel and Mellanox NICs. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Siobhan Butler <siobhan.a.butler@intel.com>
2015-01-31 22:06:06 +00:00
F: doc/guides/nics/mlx4.rst
maintainers: add drivers features files Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-05-10 13:33:50 +00:00
F: doc/guides/nics/features/mlx4.ini
mlx4: new poll mode driver This PMD manages all variants of Mellanox ConnectX-3 (EN 40, EN 10, Pro EN 40) as well as their virtual functions in SR-IOV context through IB Verbs (libibverbs) and the dedicated user-space driver (libmlx4). It is disabled by default due to dependencies on these libraries and only supports Linux userland at the moment partly because /sys (sysfs) support is required. Also claim responsibility in the MAINTAINERS file. Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com> Signed-off-by: Olga Shern <olgas@mellanox.com>
2015-02-25 13:52:05 +00:00
mlx5: introduce new driver for Mellanox ConnectX-4 adapters In its current state, this driver implements the bare minimum to initialize itself and Mellanox ConnectX-4 adapters without doing anything else (no RX/TX for instance). It is disabled by default since it is based on the mlx4 driver and also depends on libibverbs. Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com> Signed-off-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com> Signed-off-by: Or Ami <ora@mellanox.com>
2015-10-30 18:52:30 +00:00
Mellanox mlx5
maintainers: update for mlx5 PMD Matan thankfully accepted to replace myself as maintainer for mlx5 PMD. Good luck! Signed-off-by: Yongseok Koh <yskoh@mellanox.com> Acked-by: Shahaf Shuler <shahafs@mellanox.com> Acked-by: Matan Azrad <matan@mellanox.com>
2019-08-21 20:55:35 +00:00
M: Matan Azrad <matan@mellanox.com>
maintainers: update for Mellanox PMDs Shahaf and Matan volunteered to replace Nélio and myself as maintainers for mlx4 and mlx5 PMDs. Cheers! Cc: stable@dpdk.org Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com> Signed-off-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com> Acked-by: Shahaf Shuler <shahafs@mellanox.com> Acked-by: Matan Azrad <matan@mellanox.com> Acked-by: Yongseok Koh <yskoh@mellanox.com>
2018-07-05 09:19:46 +00:00
M: Shahaf Shuler <shahafs@mellanox.com>
maintainers: update for Mellanox Due to position change, cannot be a full time maintainer anymore. The git tree dpdk-next-net-mlx will be managed by Raslan, as approved by the DPDK Technical Board. For mlx5 PMD, Slava is added as additional maintainer. Will continue to be involved in the DPDK community in different ways. Signed-off-by: Shahaf Shuler <shahafs@mellanox.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
2019-07-04 10:01:04 +00:00
M: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
maintainers: update mlx drivers sub tree Mellanox PMD patches should target the next-net-mlx sub tree. Signed-off-by: Shahaf Shuler <shahafs@mellanox.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2018-01-04 20:01:07 +00:00
T: git://dpdk.org/next/dpdk-next-net-mlx
common/mlx5: introduce common library A new Mellanox vdpa PMD will be added to support vdpa operations by Mellanox adapters. This vdpa PMD design includes mlx5_glue and mlx5_devx operations and large parts of them are shared with the net/mlx5 PMD. Create a new common library in drivers/common for mlx5 PMDs. Move mlx5_glue, mlx5_devx_cmds and their dependencies to the new mlx5 common library in drivers/common. The files mlx5_devx_cmds.c, mlx5_devx_cmds.h, mlx5_glue.c, mlx5_glue.h and mlx5_prm.h are moved as is from drivers/net/mlx5 to drivers/common/mlx5. Share the log mechanism macros. Separate also the log mechanism to allow different log level control to the common library. Build files and version files are adjusted accordingly. Include lines are adjusted accordingly. Signed-off-by: Matan Azrad <matan@mellanox.com> Acked-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
2020-01-29 12:38:27 +00:00
F: drivers/common/mlx5/
mlx5: introduce new driver for Mellanox ConnectX-4 adapters In its current state, this driver implements the bare minimum to initialize itself and Mellanox ConnectX-4 adapters without doing anything else (no RX/TX for instance). It is disabled by default since it is based on the mlx4 driver and also depends on libibverbs. Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com> Signed-off-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com> Signed-off-by: Or Ami <ora@mellanox.com>
2015-10-30 18:52:30 +00:00
F: drivers/net/mlx5/
config: add static linkage of mlx dependency The libraries provided by rdma-core may be statically linked if enabling CONFIG_RTE_IBVERBS_LINK_STATIC in the make-based build. If CONFIG_RTE_BUILD_SHARED_LIB is disabled, the applications will embed the mlx PMDs with ibverbs and the mlx libraries. If CONFIG_RTE_BUILD_SHARED_LIB is enabled, the mlx PMDs will embed ibverbs and the mlx libraries. Support with meson may be added later. Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: Shahaf Shuler <shahafs@mellanox.com>
2019-01-09 14:23:19 +00:00
F: buildtools/options-ibverbs-static.sh
mlx5: add documentation Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
2015-10-30 18:52:42 +00:00
F: doc/guides/nics/mlx5.rst
maintainers: add drivers features files Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-05-10 13:33:50 +00:00
F: doc/guides/nics/features/mlx5.ini
mlx5: introduce new driver for Mellanox ConnectX-4 adapters In its current state, this driver implements the bare minimum to initialize itself and Mellanox ConnectX-4 adapters without doing anything else (no RX/TX for instance). It is disabled by default since it is based on the mlx4 driver and also depends on libibverbs. Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com> Signed-off-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com> Signed-off-by: Or Ami <ora@mellanox.com>
2015-10-30 18:52:30 +00:00
net/vdev_netvsc: introduce Hyper-V platform driver This patch lays the groundwork for this driver (draft documentation, copyright notices, code base skeleton and build system hooks). While it can be successfully compiled and invoked, it's an empty shell at this stage. Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com> Signed-off-by: Matan Azrad <matan@mellanox.com>
2018-01-18 13:51:42 +00:00
Microsoft vdev_netvsc - EXPERIMENTAL
M: Matan Azrad <matan@mellanox.com>
F: drivers/net/vdev_netvsc/
F: doc/guides/nics/vdev_netvsc.rst
net/netvsc: add Hyper-V network device The driver supports Hyper-V networking directly like virtio for KVM or vmxnet3 for VMware. This code is based off of the FreeBSD driver. The file and variable names are kept the same to help with understanding (with most of the BSD style warts removed). This version supports the latest NetVSP 6.1 version and older versions. Signed-off-by: Haiyang Zhang <haiyangz@microsoft.com> Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
2018-07-13 17:06:43 +00:00
Microsoft Hyper-V netvsc - EXPERIMENTAL
M: Stephen Hemminger <sthemmin@microsoft.com>
M: K. Y. Srinivasan <kys@microsoft.com>
M: Haiyang Zhang <haiyangz@microsoft.com>
F: drivers/net/netvsc/
net/netvsc: add documentation Matching documentation for new netvsc device. Includes a brief note about the restart issue. Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
2018-07-13 17:06:44 +00:00
F: doc/guides/nics/netvsc.rst
F: doc/guides/nics/features/netvsc.ini
net/netvsc: add Hyper-V network device The driver supports Hyper-V networking directly like virtio for KVM or vmxnet3 for VMware. This code is based off of the FreeBSD driver. The file and variable names are kept the same to help with understanding (with most of the BSD style warts removed). This version supports the latest NetVSP 6.1 version and older versions. Signed-off-by: Haiyang Zhang <haiyangz@microsoft.com> Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
2018-07-13 17:06:43 +00:00
maintainers: rename section for szedata2 driver The name of company is listed for other drivers. Use the company name also for szedata2 driver. Cards are available from Netcope rather than Cesnet. Signed-off-by: Matej Vido <vido@cesnet.cz>
2017-04-07 20:12:47 +00:00
Netcope szedata2
maintainers: update for Netcope PMDs Jan and Rastislav are leaving Netcope. Martin and Jakub will replace them as Netcope PMD maintainers. Signed-off-by: Jan Remes <remes@netcope.com>
2020-03-02 16:34:05 +00:00
M: Martin Zizka <zizka@netcope.com>
M: Jakub Neruda <neruda@netcope.com>
maintainers: rename section for szedata2 driver The name of company is listed for other drivers. Use the company name also for szedata2 driver. Cards are available from Netcope rather than Cesnet. Signed-off-by: Matej Vido <vido@cesnet.cz>
2017-04-07 20:12:47 +00:00
F: drivers/net/szedata2/
F: doc/guides/nics/szedata2.rst
maintainers: add drivers features files Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-05-10 13:33:50 +00:00
F: doc/guides/nics/features/szedata2.ini
maintainers: rename section for szedata2 driver The name of company is listed for other drivers. Use the company name also for szedata2 driver. Cards are available from Netcope rather than Cesnet. Signed-off-by: Matej Vido <vido@cesnet.cz>
2017-04-07 20:12:47 +00:00
net/nfb: add new netcope driver Added new net driver for Netcope nfb cards Signed-off-by: Rastislav Cernay <cernay@netcope.com>
2019-04-07 15:03:21 +00:00
Netcope nfb
maintainers: update for Netcope PMDs Jan and Rastislav are leaving Netcope. Martin and Jakub will replace them as Netcope PMD maintainers. Signed-off-by: Jan Remes <remes@netcope.com>
2020-03-02 16:34:05 +00:00
M: Martin Zizka <zizka@netcope.com>
M: Jakub Neruda <neruda@netcope.com>
net/nfb: add new netcope driver Added new net driver for Netcope nfb cards Signed-off-by: Rastislav Cernay <cernay@netcope.com>
2019-04-07 15:03:21 +00:00
F: drivers/net/nfb/
F: doc/guides/nics/nfb.rst
F: doc/guides/nics/features/nfb.ini
nfp: introduce driver initialization Signed-off-by: Alejandro Lucero <alejandro.lucero@netronome.com> Signed-off-by: Rolf Neugebauer <rolf.neugebauer@netronome.com>
2015-11-30 10:25:35 +00:00
Netronome nfp
maintainers: update for NFP As Alejandro is no longer with Netronome we appointed two new maintainers for the Netronome PMD Signed-off-by: Heinrich Kuhn <heinrich.kuhn@netronome.com>
2019-11-27 11:36:15 +00:00
M: Heinrich Kuhn <heinrich.kuhn@netronome.com>
nfp: introduce driver initialization Signed-off-by: Alejandro Lucero <alejandro.lucero@netronome.com> Signed-off-by: Rolf Neugebauer <rolf.neugebauer@netronome.com>
2015-11-30 10:25:35 +00:00
F: drivers/net/nfp/
nfp: add guide Signed-off-by: Alejandro Lucero <alejandro.lucero@netronome.com> Signed-off-by: Rolf Neugebauer <rolf.neugebauer@netronome.com>
2015-11-30 10:25:42 +00:00
F: doc/guides/nics/nfp.rst
doc: create different features files for NFP drivers NFP PMD implement now PF and VF drivers. Although the driver functionality is the same by now, except for initialization, it will change with future PF additions. A new feature is required for describing the firmware upload capability coming with the NFP PF now, so the PF file will be updated soon in another patch. SRIOV is not supported by the PF yet, and it is wrong to include it as a VF driver feature, so none of the files have such a feature. Signed-off-by: Alejandro Lucero <alejandro.lucero@netronome.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2017-09-01 14:12:21 +00:00
F: doc/guides/nics/features/nfp*.ini
nfp: introduce driver initialization Signed-off-by: Alejandro Lucero <alejandro.lucero@netronome.com> Signed-off-by: Rolf Neugebauer <rolf.neugebauer@netronome.com>
2015-11-30 10:25:35 +00:00
bus/dpaa: introduce NXP DPAA bus driver skeleton Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
2017-09-28 12:29:22 +00:00
NXP dpaa
M: Hemant Agrawal <hemant.agrawal@nxp.com>
maintainers: claim maintainership of NXP net PMDs Shreyansh is no longer with NXP. Pankaj is no longer working on DPDK. Signed-off-by: Sachin Saxena <sachin.saxena@nxp.com> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
2019-07-15 11:38:30 +00:00
M: Sachin Saxena <sachin.saxena@nxp.com>
mempool/dpaa: support NXP DPAA mempool This Mempool driver works with DPAA BMan hardware block. This block manages data buffers in memory, and provides efficient interface with other hardware and software components for buffer requests. This patch adds support for BMan. Compilation would be enabled in subsequent patches. Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com>
2017-09-28 12:29:39 +00:00
F: drivers/mempool/dpaa/
net/dpaa: add NXP DPAA PMD driver skeleton A skeleton which would be called after bus device scan. It currently fails to identify the device. Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com> Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com>
2017-09-28 12:29:42 +00:00
F: drivers/net/dpaa/
doc: add NXP DPAA PMD documentation Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com> Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com>
2017-09-28 12:29:37 +00:00
F: doc/guides/nics/dpaa.rst
F: doc/guides/nics/features/dpaa.ini
bus/dpaa: introduce NXP DPAA bus driver skeleton Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
2017-09-28 12:29:22 +00:00
bus/fslmc: introduce fsl-mc bus driver The fslmc bus driver is a rte_bus driver which scans the fsl-mc bus for NXP DPAA2 SoCs. Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
2017-04-11 13:37:08 +00:00
NXP dpaa2
M: Hemant Agrawal <hemant.agrawal@nxp.com>
maintainers: claim maintainership of NXP net PMDs Shreyansh is no longer with NXP. Pankaj is no longer working on DPDK. Signed-off-by: Sachin Saxena <sachin.saxena@nxp.com> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
2019-07-15 11:38:30 +00:00
M: Sachin Saxena <sachin.saxena@nxp.com>
mempool/dpaa2: add hardware offloaded mempool DPAA2 Hardware Mempool handlers allow enqueue/dequeue from NXP's QBMAN hardware block. CONFIG_RTE_MBUF_DEFAULT_MEMPOOL_OPS is set to 'dpaa2', if the pool is enabled. This memory pool currently supports packet mbuf type blocks only. Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
2017-04-11 13:42:39 +00:00
F: drivers/mempool/dpaa2/
net/dpaa2: introduce NXP DPAA2 driver add support for fsl-mc bus based dpaa2 pmd driver. Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
2017-04-11 13:49:17 +00:00
F: drivers/net/dpaa2/
doc: add DPAA2 NIC details This patch adds the NXP dpaa2 architecture and pmd details in the Network interfaces section. Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2017-04-11 13:49:18 +00:00
F: doc/guides/nics/dpaa2.rst
maintainers: add drivers features files Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-05-10 13:33:50 +00:00
F: doc/guides/nics/features/dpaa2.ini
bus/fslmc: introduce fsl-mc bus driver The fslmc bus driver is a rte_bus driver which scans the fsl-mc bus for NXP DPAA2 SoCs. Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
2017-04-11 13:37:08 +00:00
net/enetc: add PMD with basic operations This patch introduces the enetc PMD with basic initialisation functions includes probe, teardown, hardware initialisation Signed-off-by: Gagandeep Singh <g.singh@nxp.com> Acked-by: Shreyansh Jain <shreyansh.jain@nxp.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-10-03 13:36:05 +00:00
NXP enetc
M: Gagandeep Singh <g.singh@nxp.com>
maintainers: claim maintainership of NXP net PMDs Shreyansh is no longer with NXP. Pankaj is no longer working on DPDK. Signed-off-by: Sachin Saxena <sachin.saxena@nxp.com> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
2019-07-15 11:38:30 +00:00
M: Sachin Saxena <sachin.saxena@nxp.com>
net/enetc: add PMD with basic operations This patch introduces the enetc PMD with basic initialisation functions includes probe, teardown, hardware initialisation Signed-off-by: Gagandeep Singh <g.singh@nxp.com> Acked-by: Shreyansh Jain <shreyansh.jain@nxp.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-10-03 13:36:05 +00:00
F: drivers/net/enetc/
doc: add guide for ENETC PMD Add enetc usage document to compile and run the DPDK application on enetc supported platform. This document introduces the enetc driver, supported platforms and supported features. Signed-off-by: Gagandeep Singh <g.singh@nxp.com> Acked-by: Shreyansh Jain <shreyansh.jain@nxp.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-10-03 13:36:08 +00:00
F: doc/guides/nics/enetc.rst
net/enetc: add PMD with basic operations This patch introduces the enetc PMD with basic initialisation functions includes probe, teardown, hardware initialisation Signed-off-by: Gagandeep Singh <g.singh@nxp.com> Acked-by: Shreyansh Jain <shreyansh.jain@nxp.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-10-03 13:36:05 +00:00
F: doc/guides/nics/features/enetc.ini
net/pfe: introduce basic functions pfe (packet forwarding engine) is a network poll mode driver for NXP SoC ls1012a. This patch introduces the framework of pfe driver with basic functions of initialisation and teardown. Signed-off-by: Gagandeep Singh <g.singh@nxp.com> Signed-off-by: Akhil Goyal <akhil.goyal@nxp.com> Acked-by: Nipun Gupta <nipun.gupta@nxp.com>
2019-10-10 06:32:22 +00:00
NXP pfe
M: Gagandeep Singh <g.singh@nxp.com>
M: Akhil Goyal <akhil.goyal@nxp.com>
F: doc/guides/nics/pfe.rst
F: drivers/net/pfe/
F: doc/guides/nics/features/pfe.ini
net/ionic: add skeleton Add makefile and config file options to compile the Pensando ionic PMD. Add feature and version map file. Update maintainers file. Signed-off-by: Alfredo Cardigliano <cardigliano@ntop.org> Reviewed-by: Shannon Nelson <snelson@pensando.io>
2020-01-19 15:53:39 +00:00
Pensando ionic
M: Alfredo Cardigliano <cardigliano@ntop.org>
F: drivers/net/ionic/
F: doc/guides/nics/ionic.rst
F: doc/guides/nics/features/ionic.ini
bnx2x: add maintainers Add maintainers for BNX2X PMD. Signed-off-by: Rasesh Mody <rasesh.mody@qlogic.com>
2015-12-11 06:36:41 +00:00
QLogic bnx2x
maintainers: update Cavium email ids Following Marvell's acquisition of Cavium, we need to update all the Cavium maintainer's entries to point to our new e-mail addresses. Update maintainers as they are no longer working for Cavium. Thanks to Harish Patil for his support and development of our various dpdk drivers. Signed-off-by: Jerin Jacob <jerinj@marvell.com>
2018-12-16 15:43:25 +00:00
M: Rasesh Mody <rmody@marvell.com>
M: Shahed Shaikh <shshaikh@marvell.com>
maintainers: claim maintainership of net-mrvl sub-tree Claim the maintainership of the sub tree dpdk-next-net-mrvl, which covers all the Marvell network PMDs. Signed-off-by: Jerin Jacob <jerinj@marvell.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2019-06-25 05:42:41 +00:00
T: git://dpdk.org/next/dpdk-next-net-mrvl
bnx2x: add maintainers Add maintainers for BNX2X PMD. Signed-off-by: Rasesh Mody <rasesh.mody@qlogic.com>
2015-12-11 06:36:41 +00:00
F: drivers/net/bnx2x/
F: doc/guides/nics/bnx2x.rst
maintainers: add drivers features files Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-05-10 13:33:50 +00:00
F: doc/guides/nics/features/bnx2x*.ini
bnx2x: add maintainers Add maintainers for BNX2X PMD. Signed-off-by: Rasesh Mody <rasesh.mody@qlogic.com>
2015-12-11 06:36:41 +00:00
qede: add base driver The base driver is the backend module for the QLogic FastLinQ QL4xxxx 25G/40G CNA family of adapters as well as their virtual functions (VF) in SR-IOV context. The purpose of the base module is to: - provide all the common code that will be shared between the various drivers that would be used with said line of products. Flows such as chip initialization and de-initialization fall under this category. - abstract the protocol-specific HW & FW components, allowing the protocol drivers to have clean APIs, which are detached in its slowpath configuration from the actual Hardware Software Interface(HSI). This patch adds a base module without any protocol-specific bits. I.e., this adds a basic implementation that almost entirely falls under the first category. Signed-off-by: Harish Patil <harish.patil@qlogic.com> Signed-off-by: Rasesh Mody <rasesh.mody@qlogic.com> Signed-off-by: Sony Chacko <sony.chacko@qlogic.com>
2016-04-27 14:18:36 +00:00
QLogic qede PMD
maintainers: update Cavium email ids Following Marvell's acquisition of Cavium, we need to update all the Cavium maintainer's entries to point to our new e-mail addresses. Update maintainers as they are no longer working for Cavium. Thanks to Harish Patil for his support and development of our various dpdk drivers. Signed-off-by: Jerin Jacob <jerinj@marvell.com>
2018-12-16 15:43:25 +00:00
M: Rasesh Mody <rmody@marvell.com>
M: Shahed Shaikh <shshaikh@marvell.com>
maintainers: claim maintainership of net-mrvl sub-tree Claim the maintainership of the sub tree dpdk-next-net-mrvl, which covers all the Marvell network PMDs. Signed-off-by: Jerin Jacob <jerinj@marvell.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2019-06-25 05:42:41 +00:00
T: git://dpdk.org/next/dpdk-next-net-mrvl
qede: add base driver The base driver is the backend module for the QLogic FastLinQ QL4xxxx 25G/40G CNA family of adapters as well as their virtual functions (VF) in SR-IOV context. The purpose of the base module is to: - provide all the common code that will be shared between the various drivers that would be used with said line of products. Flows such as chip initialization and de-initialization fall under this category. - abstract the protocol-specific HW & FW components, allowing the protocol drivers to have clean APIs, which are detached in its slowpath configuration from the actual Hardware Software Interface(HSI). This patch adds a base module without any protocol-specific bits. I.e., this adds a basic implementation that almost entirely falls under the first category. Signed-off-by: Harish Patil <harish.patil@qlogic.com> Signed-off-by: Rasesh Mody <rasesh.mody@qlogic.com> Signed-off-by: Sony Chacko <sony.chacko@qlogic.com>
2016-04-27 14:18:36 +00:00
F: drivers/net/qede/
qede: add core driver The Qlogic Everest Driver for Ethernet(QEDE) Poll Mode Driver(PMD) is the DPDK specific module for QLogic FastLinQ QL4xxxx 25G/40G CNA family of adapters as well as their virtual functions (VF) in SR-IOV context. This patch adds QEDE PMD, which interacts with base driver and initialises the HW. This patch content also includes: - eth_dev_ops callbacks - Rx/Tx support for the driver - link default configuration - change link property - link up/down/update notifications - vlan offload and filtering capability - device/function/port statistics - qede nic guide and updated overview.rst Note that the follow on commits contain the code for the features mentioned in documents but not implemented in this patch. Signed-off-by: Harish Patil <harish.patil@qlogic.com> Signed-off-by: Rasesh Mody <rasesh.mody@qlogic.com> Signed-off-by: Sony Chacko <sony.chacko@qlogic.com>
2016-04-27 14:18:37 +00:00
F: doc/guides/nics/qede.rst
maintainers: add drivers features files Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-05-10 13:33:50 +00:00
F: doc/guides/nics/features/qede*.ini
qede: add base driver The base driver is the backend module for the QLogic FastLinQ QL4xxxx 25G/40G CNA family of adapters as well as their virtual functions (VF) in SR-IOV context. The purpose of the base module is to: - provide all the common code that will be shared between the various drivers that would be used with said line of products. Flows such as chip initialization and de-initialization fall under this category. - abstract the protocol-specific HW & FW components, allowing the protocol drivers to have clean APIs, which are detached in its slowpath configuration from the actual Hardware Software Interface(HSI). This patch adds a base module without any protocol-specific bits. I.e., this adds a basic implementation that almost entirely falls under the first category. Signed-off-by: Harish Patil <harish.patil@qlogic.com> Signed-off-by: Rasesh Mody <rasesh.mody@qlogic.com> Signed-off-by: Sony Chacko <sony.chacko@qlogic.com>
2016-04-27 14:18:36 +00:00
net/sfc: libefx-based driver stub Enable the PMD by default on supported configurations. Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com> Reviewed-by: Andy Moreton <amoreton@solarflare.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
2016-11-29 16:18:33 +00:00
Solarflare sfc_efx
M: Andrew Rybchenko <arybchenko@solarflare.com>
F: drivers/net/sfc/
F: doc/guides/nics/sfc_efx.rst
F: doc/guides/nics/features/sfc_efx.ini
maintainers: split virtio and vhost Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2017-01-12 06:24:58 +00:00
VMware vmxnet3
maintainers: claim responsibility for vmxnet3 Signed-off-by: Yong Wang <yongwang@vmware.com>
2018-03-30 21:57:02 +00:00
M: Yong Wang <yongwang@vmware.com>
maintainers: split virtio and vhost Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2017-01-12 06:24:58 +00:00
F: drivers/net/vmxnet3/
F: doc/guides/nics/vmxnet3.rst
maintainers: add drivers features files Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-05-10 13:33:50 +00:00
F: doc/guides/nics/features/vmxnet3.ini
maintainers: split virtio and vhost Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2017-01-12 06:24:58 +00:00
Vhost-user
maintainers: claim responsibility for vhost and virtio Add myself as co-maintainer for vhost/virtio drivers and vhost-user library. Suggested-by: Yuanhan Liu <yuanhan.liu@linux.intel.com> Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com> Acked-by: Yuanhan Liu <yuanhan.liu@linux.intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2017-02-17 08:31:42 +00:00
M: Maxime Coquelin <maxime.coquelin@redhat.com>
maintainers: add vhost and virtio co-maintainers Add Tiwei and Zhihong as co-maintainers for the Vhost and Virtio components. They have done great contributions recently, and been very helpful in helping to review Vhost and Virtio series. Also, add Tiwei as backup for the Next-virtio tree. Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com> Acked-by: Tiwei Bie <tiwei.bie@intel.com> Acked-by: Zhihong Wang <zhihong.wang@intel.com> Acked-by: Zhiyong Yang <zhiyong.yang@intel.com>
2018-06-12 08:01:27 +00:00
M: Zhihong Wang <zhihong.wang@intel.com>
maintainers: update for virtio and vhost I volunteer to be co-maintainer for Vhost-user/Vhost PMD/Virtio PMD. Signed-off-by: Xiaolong Ye <xiaolong.ye@intel.com> Acked-by: Tiwei Bie <tiwei.bie@intel.com> Acked-by: Zhihong Wang <zhihong.wang@intel.com> Acked-by: Maxime Coquelin <maxime.coquelin@redhat.com>
2020-02-21 13:35:39 +00:00
M: Xiaolong Ye <xiaolong.ye@intel.com>
maintainers: add git tree for virtio/vhost Add a git tree line for the virtio/vhost section, to make an explicit statement that the developers are suggested to make patches based on that tree. Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2016-07-19 04:17:49 +00:00
T: git://dpdk.org/next/dpdk-next-virtio
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: lib/librte_vhost/
F: doc/guides/prog_guide/vhost_lib.rst
F: examples/vhost/
F: doc/guides/sample_app_ug/vhost.rst
examples/vhost_blk: introduce vhost storage sample A Vhost-blk example that support inflight feature. It uses the new APIs that introduced in the first patch, so it can show how these APIs work to support inflight feature. Signed-off-by: Jin Yu <jin.yu@intel.com> Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
2019-11-04 16:36:26 +00:00
F: examples/vhost_blk/
F: doc/guides/sample_app_ug/vhost_blk.rst
examples/vhost_crypto: add sample application This patch adds vhost_crypto sample application to DPDK. Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com> Acked-by: Jay Zhou <jianjay.zhou@huawei.com> Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
2018-04-05 16:01:36 +00:00
F: examples/vhost_crypto/
examples/vdpa: introduce a new sample for vDPA The vdpa sample application creates vhost-user sockets by using the vDPA backend. vDPA stands for vhost Data Path Acceleration which utilizes virtio ring compatible devices to serve virtio driver directly to enable datapath acceleration. As vDPA driver can help to set up vhost datapath, this application doesn't need to launch dedicated worker threads for vhost enqueue/dequeue operations. Signed-off-by: Xiaolong Ye <xiaolong.ye@intel.com> Acked-by: Xiao Wang <xiao.w.wang@intel.com> Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
2018-09-28 21:47:47 +00:00
F: examples/vdpa/
F: doc/guides/sample_app_ug/vdpa.rst
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
vhost: add driver on top of the library The patch introduces a new PMD. This PMD is implemented as thin wrapper of librte_vhost. It means librte_vhost is also needed to compile the PMD. The vhost messages will be handled only when a port is started. So start a port first, then invoke QEMU. The PMD has 2 parameters. - iface: The parameter is used to specify a path to connect to a virtio-net device. - queues: The parameter is used to specify the number of the queues virtio-net device has. (Default: 1) Here is an example. $ ./testpmd -c f -n 4 --vdev 'eth_vhost0,iface=/tmp/sock0,queues=1' -- -i To connect above testpmd, here is qemu command example. $ qemu-system-x86_64 \ <snip> -chardev socket,id=chr0,path=/tmp/sock0 \ -netdev vhost-user,id=net0,chardev=chr0,vhostforce,queues=1 \ -device virtio-net-pci,netdev=net0,mq=on Signed-off-by: Tetsuya Mukawa <mukawa@igel.co.jp> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Yuanhan Liu <yuanhan.liu@linux.intel.com> Acked-by: Rich Lane <rich.lane@bigswitch.com> Tested-by: Rich Lane <rich.lane@bigswitch.com> Update for queue state event name: Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2016-03-21 05:45:08 +00:00
Vhost PMD
maintainers: claim responsibility for vhost and virtio Add myself as co-maintainer for vhost/virtio drivers and vhost-user library. Suggested-by: Yuanhan Liu <yuanhan.liu@linux.intel.com> Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com> Acked-by: Yuanhan Liu <yuanhan.liu@linux.intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2017-02-17 08:31:42 +00:00
M: Maxime Coquelin <maxime.coquelin@redhat.com>
maintainers: add vhost and virtio co-maintainers Add Tiwei and Zhihong as co-maintainers for the Vhost and Virtio components. They have done great contributions recently, and been very helpful in helping to review Vhost and Virtio series. Also, add Tiwei as backup for the Next-virtio tree. Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com> Acked-by: Tiwei Bie <tiwei.bie@intel.com> Acked-by: Zhihong Wang <zhihong.wang@intel.com> Acked-by: Zhiyong Yang <zhiyong.yang@intel.com>
2018-06-12 08:01:27 +00:00
M: Zhihong Wang <zhihong.wang@intel.com>
maintainers: update for virtio and vhost I volunteer to be co-maintainer for Vhost-user/Vhost PMD/Virtio PMD. Signed-off-by: Xiaolong Ye <xiaolong.ye@intel.com> Acked-by: Tiwei Bie <tiwei.bie@intel.com> Acked-by: Zhihong Wang <zhihong.wang@intel.com> Acked-by: Maxime Coquelin <maxime.coquelin@redhat.com>
2020-02-21 13:35:39 +00:00
M: Xiaolong Ye <xiaolong.ye@intel.com>
maintainers: add git tree for virtio/vhost Add a git tree line for the virtio/vhost section, to make an explicit statement that the developers are suggested to make patches based on that tree. Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2016-07-19 04:17:49 +00:00
T: git://dpdk.org/next/dpdk-next-virtio
vhost: add driver on top of the library The patch introduces a new PMD. This PMD is implemented as thin wrapper of librte_vhost. It means librte_vhost is also needed to compile the PMD. The vhost messages will be handled only when a port is started. So start a port first, then invoke QEMU. The PMD has 2 parameters. - iface: The parameter is used to specify a path to connect to a virtio-net device. - queues: The parameter is used to specify the number of the queues virtio-net device has. (Default: 1) Here is an example. $ ./testpmd -c f -n 4 --vdev 'eth_vhost0,iface=/tmp/sock0,queues=1' -- -i To connect above testpmd, here is qemu command example. $ qemu-system-x86_64 \ <snip> -chardev socket,id=chr0,path=/tmp/sock0 \ -netdev vhost-user,id=net0,chardev=chr0,vhostforce,queues=1 \ -device virtio-net-pci,netdev=net0,mq=on Signed-off-by: Tetsuya Mukawa <mukawa@igel.co.jp> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Yuanhan Liu <yuanhan.liu@linux.intel.com> Acked-by: Rich Lane <rich.lane@bigswitch.com> Tested-by: Rich Lane <rich.lane@bigswitch.com> Update for queue state event name: Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2016-03-21 05:45:08 +00:00
F: drivers/net/vhost/
maintainers: add missing doc references Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-05-22 14:28:30 +00:00
F: doc/guides/nics/vhost.rst
maintainers: add drivers features files Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-05-10 13:33:50 +00:00
F: doc/guides/nics/features/vhost.ini
vhost: add driver on top of the library The patch introduces a new PMD. This PMD is implemented as thin wrapper of librte_vhost. It means librte_vhost is also needed to compile the PMD. The vhost messages will be handled only when a port is started. So start a port first, then invoke QEMU. The PMD has 2 parameters. - iface: The parameter is used to specify a path to connect to a virtio-net device. - queues: The parameter is used to specify the number of the queues virtio-net device has. (Default: 1) Here is an example. $ ./testpmd -c f -n 4 --vdev 'eth_vhost0,iface=/tmp/sock0,queues=1' -- -i To connect above testpmd, here is qemu command example. $ qemu-system-x86_64 \ <snip> -chardev socket,id=chr0,path=/tmp/sock0 \ -netdev vhost-user,id=net0,chardev=chr0,vhostforce,queues=1 \ -device virtio-net-pci,netdev=net0,mq=on Signed-off-by: Tetsuya Mukawa <mukawa@igel.co.jp> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Yuanhan Liu <yuanhan.liu@linux.intel.com> Acked-by: Rich Lane <rich.lane@bigswitch.com> Tested-by: Rich Lane <rich.lane@bigswitch.com> Update for queue state event name: Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2016-03-21 05:45:08 +00:00
maintainers: split virtio and vhost Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2017-01-12 06:24:58 +00:00
Virtio PMD
maintainers: claim responsibility for vhost and virtio Add myself as co-maintainer for vhost/virtio drivers and vhost-user library. Suggested-by: Yuanhan Liu <yuanhan.liu@linux.intel.com> Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com> Acked-by: Yuanhan Liu <yuanhan.liu@linux.intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2017-02-17 08:31:42 +00:00
M: Maxime Coquelin <maxime.coquelin@redhat.com>
maintainers: add vhost and virtio co-maintainers Add Tiwei and Zhihong as co-maintainers for the Vhost and Virtio components. They have done great contributions recently, and been very helpful in helping to review Vhost and Virtio series. Also, add Tiwei as backup for the Next-virtio tree. Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com> Acked-by: Tiwei Bie <tiwei.bie@intel.com> Acked-by: Zhihong Wang <zhihong.wang@intel.com> Acked-by: Zhiyong Yang <zhiyong.yang@intel.com>
2018-06-12 08:01:27 +00:00
M: Zhihong Wang <zhihong.wang@intel.com>
maintainers: update for virtio and vhost I volunteer to be co-maintainer for Vhost-user/Vhost PMD/Virtio PMD. Signed-off-by: Xiaolong Ye <xiaolong.ye@intel.com> Acked-by: Tiwei Bie <tiwei.bie@intel.com> Acked-by: Zhihong Wang <zhihong.wang@intel.com> Acked-by: Maxime Coquelin <maxime.coquelin@redhat.com>
2020-02-21 13:35:39 +00:00
M: Xiaolong Ye <xiaolong.ye@intel.com>
maintainers: split virtio and vhost Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2017-01-12 06:24:58 +00:00
T: git://dpdk.org/next/dpdk-next-virtio
F: drivers/net/virtio/
F: doc/guides/nics/virtio.rst
maintainers: add drivers features files Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-05-10 13:33:50 +00:00
F: doc/guides/nics/features/virtio*.ini
maintainers: split virtio and vhost Signed-off-by: Yuanhan Liu <yuanhan.liu@linux.intel.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2017-01-12 06:24:58 +00:00
net/avp: add base files This commit introduces the AVP PMD file structure without adding any actual driver functionality. Functional blocks will be added in later patches. Signed-off-by: Allain Legacy <allain.legacy@windriver.com> Signed-off-by: Matt Peters <matt.peters@windriver.com> Acked-by: Vincent Jardin <vincent.jardin@6wind.com>
2017-03-28 11:53:56 +00:00
Wind River AVP
maintainers: replace for AVP Resigning my maintainership of the AVP driver and adding Steve Webster as a new maintainer. Signed-off-by: Allain Legacy <allain.legacy@windriver.com>
2019-11-07 20:48:34 +00:00
M: Steven Webster <steven.webster@windriver.com>
net/avp: add base files This commit introduces the AVP PMD file structure without adding any actual driver functionality. Functional blocks will be added in later patches. Signed-off-by: Allain Legacy <allain.legacy@windriver.com> Signed-off-by: Matt Peters <matt.peters@windriver.com> Acked-by: Vincent Jardin <vincent.jardin@6wind.com>
2017-03-28 11:53:56 +00:00
M: Matt Peters <matt.peters@windriver.com>
F: drivers/net/avp/
doc: add AVP Updates the documentation and feature lists for the AVP PMD device. Signed-off-by: Allain Legacy <allain.legacy@windriver.com> Signed-off-by: Matt Peters <matt.peters@windriver.com> Acked-by: John McNamara <john.mcnamara@intel.com> Acked-by: Vincent Jardin <vincent.jardin@6wind.com>
2017-03-28 11:54:09 +00:00
F: doc/guides/nics/avp.rst
maintainers: add drivers features files Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-05-10 13:33:50 +00:00
F: doc/guides/nics/features/avp.ini
net/avp: add base files This commit introduces the AVP PMD file structure without adding any actual driver functionality. Functional blocks will be added in later patches. Signed-off-by: Allain Legacy <allain.legacy@windriver.com> Signed-off-by: Matt Peters <matt.peters@windriver.com> Acked-by: Vincent Jardin <vincent.jardin@6wind.com>
2017-03-28 11:53:56 +00:00
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
PCAP PMD
maintainers: claim responsibility for pcap PMD Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-04-08 17:03:28 +00:00
M: Ferruh Yigit <ferruh.yigit@intel.com>
pcap: move drivers/net/ Move pcap pmd to drivers/net directory Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: John McNamara <john.mcnamara@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-05-15 15:56:56 +00:00
F: drivers/net/pcap/
doc: nics guide Create nics guide by moving chapters about Intel and Mellanox NICs. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Siobhan Butler <siobhan.a.butler@intel.com>
2015-01-31 22:06:06 +00:00
F: doc/guides/nics/pcap_ring.rst
maintainers: add drivers features files Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-05-10 13:33:50 +00:00
F: doc/guides/nics/features/pcap.ini
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
net/tap: add TUN/TAP device PMD The PMD allows for DPDK and the host to communicate using a raw device interface on the host and in the DPDK application. The device created is a Tap device with a L2 packet header. Signed-off-by: Keith Wiles <keith.wiles@intel.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com> Tested-by: Aws Ismail <aismail@ciena.com> Tested-by: Vasily Philipov <vasilyf@mellanox.com>
2016-12-12 14:38:38 +00:00
Tap PMD
maintainers: hand off ownership of tap PMD I have unfortunately no longer time enough for maintaining Tap PMD. Keith has kindly volunteered to take over maintainership. He's been at the origin of this PMD and knows well how it works. Signed-off-by: Pascal Mazon <pascal.mazon@6wind.com> Acked-by: Keith Wiles <keith.wiles@intel.com>
2018-05-17 09:44:58 +00:00
M: Keith Wiles <keith.wiles@intel.com>
net/tap: add TUN/TAP device PMD The PMD allows for DPDK and the host to communicate using a raw device interface on the host and in the DPDK application. The device created is a Tap device with a L2 packet header. Signed-off-by: Keith Wiles <keith.wiles@intel.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com> Tested-by: Aws Ismail <aismail@ciena.com> Tested-by: Vasily Philipov <vasilyf@mellanox.com>
2016-12-12 14:38:38 +00:00
F: drivers/net/tap/
F: doc/guides/nics/tap.rst
maintainers: add drivers features files Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-05-10 13:33:50 +00:00
F: doc/guides/nics/features/tap.ini
net/tap: add TUN/TAP device PMD The PMD allows for DPDK and the host to communicate using a raw device interface on the host and in the DPDK application. The device created is a Tap device with a L2 packet header. Signed-off-by: Keith Wiles <keith.wiles@intel.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com> Tested-by: Aws Ismail <aismail@ciena.com> Tested-by: Vasily Philipov <vasilyf@mellanox.com>
2016-12-12 14:38:38 +00:00
net/kni: add KNI PMD Add KNI PMD which wraps librte_kni for ease of use. KNI PMD can be used as any regular PMD to send / receive packets to the Linux networking stack. Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Reviewed-by: Yong Wang <yongwang@vmware.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: Yong Wang <yongwang@vmware.com>
2017-02-17 13:42:38 +00:00
KNI PMD
M: Ferruh Yigit <ferruh.yigit@intel.com>
F: drivers/net/kni/
F: doc/guides/nics/kni.rst
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
Ring PMD
maintainers: claim ring pmd library Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-03-11 10:31:54 +00:00
M: Bruce Richardson <bruce.richardson@intel.com>
ring: move to drivers/net/ Move ring PMD to drivers directory Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: John McNamara <john.mcnamara@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-05-15 15:56:57 +00:00
F: drivers/net/ring/
doc: nics guide Create nics guide by moving chapters about Intel and Mellanox NICs. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Siobhan Butler <siobhan.a.butler@intel.com>
2015-01-31 22:06:06 +00:00
F: doc/guides/nics/pcap_ring.rst
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_pmd_ring.c
F: app/test/test_pmd_ring_perf.c
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
maintainers: split networking and crypto drivers There are now 2 different sections for drivers/net/ and drivers/crypto/. It makes possible to declare some dedicated git trees. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2016-07-20 10:34:45 +00:00
Null Networking PMD
maintainers: update email address Signed-off-by: Tetsuya Mukawa <mukawa@igel.co.jp>
2016-07-28 05:53:59 +00:00
M: Tetsuya Mukawa <mtetsuyah@gmail.com>
null: move to drivers/net/ Move null PMD to drivers/net directory Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: John McNamara <john.mcnamara@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-05-15 15:56:55 +00:00
F: drivers/net/null/
null: new poll mode driver Null PMD is a driver of the virtual device particularly designed to measure performance of DPDK PMDs. When an application call rx, Null PMD just allocates mbufs and returns those. Also tx, the PMD just frees mbufs. The PMD has following options. - size: specify packe size allocated by RX. Default packet size is 64. - copy: specify 1 or 0 to enable or disable copy while RX and TX. Default value is 0(disabled). This option is used for emulating more realistic data transfer. Copy size is equal to packet size. To use the PMD, enable CONFIG_RTE_BUILD_SHARED_LIB in config file. Then compile the PMD as shared library. The library can be linked using '-d' option when an application invokes. Here is an example. $ sudo ./testpmd -c f -n 4 -d librte_pmd_null.so \ --vdev 'eth_null0' --vdev 'eth_null1' -- -i --no-flush-rx If testpmd is compiled with CONFIG_RTE_BUILD_SHARED_LIB, it may need to specify more libraries using '-d' option. Signed-off-by: Tetsuya Mukawa <mukawa@igel.co.jp> Acked-by: Bernard Iremonger <bernard.iremonger@intel.com>
2015-02-23 05:12:34 +00:00
net/failsafe: add fail-safe PMD Introduce the fail-safe poll mode driver initialization and enable its build infrastructure. This PMD allows for applications to benefit from true hot-plugging support without having to implement it. It intercepts and manages Ethernet device removal events issued by slave PMDs and re-initializes them transparently when brought back. It also allows defining a contingency to the removal of a device, by designating a fail-over device that will take on transmitting operations if the preferred device is removed. Applications only see a fail-safe instance, without caring for underlying activity ensuring their continued operations. Signed-off-by: Gaetan Rivet <gaetan.rivet@6wind.com> Acked-by: Olga Shern <olgas@mellanox.com>
2017-07-18 12:48:14 +00:00
Fail-safe PMD
maintainers: update for failsafe and PCI library My email address has changed, gaetan.rivet@6wind.com is no longer valid. Cc: stable@dpdk.org Signed-off-by: Gaetan Rivet <grive@u256.net>
2020-01-08 14:13:32 +00:00
M: Gaetan Rivet <grive@u256.net>
net/failsafe: add fail-safe PMD Introduce the fail-safe poll mode driver initialization and enable its build infrastructure. This PMD allows for applications to benefit from true hot-plugging support without having to implement it. It intercepts and manages Ethernet device removal events issued by slave PMDs and re-initializes them transparently when brought back. It also allows defining a contingency to the removal of a device, by designating a fail-over device that will take on transmitting operations if the preferred device is removed. Applications only see a fail-safe instance, without caring for underlying activity ensuring their continued operations. Signed-off-by: Gaetan Rivet <gaetan.rivet@6wind.com> Acked-by: Olga Shern <olgas@mellanox.com>
2017-07-18 12:48:14 +00:00
F: drivers/net/failsafe/
F: doc/guides/nics/fail_safe.rst
maintainers: add missing doc references Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-05-22 14:28:30 +00:00
F: doc/guides/nics/features/failsafe.ini
net/failsafe: add fail-safe PMD Introduce the fail-safe poll mode driver initialization and enable its build infrastructure. This PMD allows for applications to benefit from true hot-plugging support without having to implement it. It intercepts and manages Ethernet device removal events issued by slave PMDs and re-initializes them transparently when brought back. It also allows defining a contingency to the removal of a device, by designating a fail-over device that will take on transmitting operations if the preferred device is removed. Applications only see a fail-safe instance, without caring for underlying activity ensuring their continued operations. Signed-off-by: Gaetan Rivet <gaetan.rivet@6wind.com> Acked-by: Olga Shern <olgas@mellanox.com>
2017-07-18 12:48:14 +00:00
net/softnic: add softnic PMD Add SoftNIC PMD to provide SW fall-back for ethdev APIs. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com> Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2017-10-10 10:18:14 +00:00
Softnic PMD
M: Jasvinder Singh <jasvinder.singh@intel.com>
M: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
F: drivers/net/softnic/
doc: add softnic documentation Add softnic documentation to NIC drivers guide. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com> Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com>
2018-07-24 15:50:24 +00:00
F: doc/guides/nics/softnic.rst
net/softnic: add softnic PMD Add SoftNIC PMD to provide SW fall-back for ethdev APIs. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com> Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2017-10-10 10:18:14 +00:00
net/memif: introduce memory interface PMD Shared memory packet interface (memif) PMD allows for DPDK and any other client using memif (DPDK, VPP, libmemif) to communicate using shared memory. The created device transmits packets in a raw format. It can be used with Ethernet mode, IP mode, or Punt/Inject. At this moment, only Ethernet mode is supported in DPDK memif implementation. Memif is Linux only. Signed-off-by: Jakub Grajciar <jgrajcia@cisco.com> Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
2019-06-06 11:38:50 +00:00
Memif PMD
M: Jakub Grajciar <jgrajcia@cisco.com>
F: drivers/net/memif/
F: doc/guides/nics/memif.rst
F: doc/guides/nics/features/memif.ini
maintainers: split networking and crypto drivers There are now 2 different sections for drivers/net/ and drivers/crypto/. It makes possible to declare some dedicated git trees. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2016-07-20 10:34:45 +00:00
Crypto Drivers
--------------
maintainers: claim responsability for crypto subtree From 16.07, I will be the maintainer of the crypto subtree. This will include: - app/test/test_cryptodev* - doc/guides/cryptodevs/ - drivers/crypto/ - examples/l2fwd-crypto/ - examples/ipsec-secgw/ - lib/librte_cryptodev/ Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2016-09-15 23:25:32 +00:00
T: git://dpdk.org/next/dpdk-next-crypto
maintainers: add drivers features files Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-05-10 13:33:50 +00:00
F: doc/guides/cryptodevs/features/default.ini
maintainers: split networking and crypto drivers There are now 2 different sections for drivers/net/ and drivers/crypto/. It makes possible to declare some dedicated git trees. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2016-07-20 10:34:45 +00:00
crypto/ccp: add AMD ccp skeleton PMD Added DPDK crypto PMD for AMD Cryptographic Co-Processors. This patch adds a basic skeleton for PMD. Signed-off-by: Ravi Kumar <ravi1.kumar@amd.com>
2018-03-19 12:23:35 +00:00
AMD CCP Crypto
maintainers: update for AMD axgbe and CCP crypto Ownership change. Signed-off-by: Amaranath Somalapuram <asomalap@amd.com> Acked-by: Ravi Kumar <ravi1.kumar@amd.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
2020-04-27 06:11:45 +00:00
M: Somalapuram Amaranath <asomalap@amd.com>
crypto/ccp: add AMD ccp skeleton PMD Added DPDK crypto PMD for AMD Cryptographic Co-Processors. This patch adds a basic skeleton for PMD. Signed-off-by: Ravi Kumar <ravi1.kumar@amd.com>
2018-03-19 12:23:35 +00:00
F: drivers/crypto/ccp/
doc: add AMD CCP guide Signed-off-by: Ravi Kumar <ravi1.kumar@amd.com>
2018-03-19 12:23:53 +00:00
F: doc/guides/cryptodevs/ccp.rst
F: doc/guides/cryptodevs/features/ccp.ini
crypto/ccp: add AMD ccp skeleton PMD Added DPDK crypto PMD for AMD Cryptographic Co-Processors. This patch adds a basic skeleton for PMD. Signed-off-by: Ravi Kumar <ravi1.kumar@amd.com>
2018-03-19 12:23:35 +00:00
maintainers: sort crypto drivers list In order to improve consistency, the list of crypto drivers are sorted alphabetically and the word PMD is removed from their names. Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-10-13 13:52:08 +00:00
ARMv8 Crypto
maintainers: update armv8 crypto PMD It is expected to update this PMD to be in line with Arm's crypto library. Update the maintainership to refect the change. Signed-off-by: Ruifeng Wang <ruifeng.wang@arm.com> Reviewed-by: Gavin Hu <gavin.hu@arm.com> Acked-by: Jerin Jacob <jerinj@marvell.com>
2019-11-27 08:47:08 +00:00
M: Ruifeng Wang <ruifeng.wang@arm.com>
crypto/armv8: add PMD optimized for ARMv8 processors This patch introduces crypto poll mode driver using ARMv8 cryptographic extensions. CPU compatibility with this driver is detected in run-time and virtual crypto device will not be created if CPU doesn't provide: AES, SHA1, SHA2 and NEON. This PMD is optimized to provide performance boost for chained crypto operations processing, such as encryption + HMAC generation, decryption + HMAC validation. In particular, cipher only or hash only operations are not provided. The driver currently supports AES-128-CBC in combination with: SHA256 HMAC and SHA1 HMAC and relies on the external armv8_crypto library: https://github.com/caviumnetworks/armv8_crypto Build ARMv8 crypto PMD if compiling for ARM64 and CONFIG_RTE_LIBRTE_PMD_ARMV8_CRYPTO option is enable in the configuration file. ARMV8_CRYPTO_LIB_PATH environment variable will point to the appropriate library directory. Signed-off-by: Zbigniew Bodek <zbigniew.bodek@caviumnetworks.com> Reviewed-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2017-01-18 20:01:54 +00:00
F: drivers/crypto/armv8/
crypto/armv8: add documentation Add documentation about the driver and update release notes. Signed-off-by: Zbigniew Bodek <zbigniew.bodek@caviumnetworks.com> Reviewed-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2017-01-18 20:01:58 +00:00
F: doc/guides/cryptodevs/armv8.rst
maintainers: add drivers features files Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-05-10 13:33:50 +00:00
F: doc/guides/cryptodevs/features/armv8.ini
crypto/armv8: add PMD optimized for ARMv8 processors This patch introduces crypto poll mode driver using ARMv8 cryptographic extensions. CPU compatibility with this driver is detected in run-time and virtual crypto device will not be created if CPU doesn't provide: AES, SHA1, SHA2 and NEON. This PMD is optimized to provide performance boost for chained crypto operations processing, such as encryption + HMAC generation, decryption + HMAC validation. In particular, cipher only or hash only operations are not provided. The driver currently supports AES-128-CBC in combination with: SHA256 HMAC and SHA1 HMAC and relies on the external armv8_crypto library: https://github.com/caviumnetworks/armv8_crypto Build ARMv8 crypto PMD if compiling for ARM64 and CONFIG_RTE_LIBRTE_PMD_ARMV8_CRYPTO option is enable in the configuration file. ARMV8_CRYPTO_LIB_PATH environment variable will point to the appropriate library directory. Signed-off-by: Zbigniew Bodek <zbigniew.bodek@caviumnetworks.com> Reviewed-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2017-01-18 20:01:54 +00:00
crypto/octeontx: add PMD skeleton Adding OCTEON TX crypto PMD skeleton. Updating the maintainers files to claim responsibility. Also enabling driver by default by adding the component in common_base. Signed-off-by: Ankur Dwivedi <ankur.dwivedi@caviumnetworks.com> Signed-off-by: Anoob Joseph <anoob.joseph@caviumnetworks.com> Signed-off-by: Murthy NSSR <nidadavolu.murthy@caviumnetworks.com> Signed-off-by: Nithin Dabilpuram <nithin.dabilpuram@caviumnetworks.com> Signed-off-by: Ragothaman Jayaraman <rjayaraman@caviumnetworks.com> Signed-off-by: Srisivasubramanian S <ssrinivasan@caviumnetworks.com> Signed-off-by: Tejasree Kondoj <kondoj.tejasree@caviumnetworks.com>
2018-10-09 09:07:34 +00:00
Cavium OCTEON TX crypto
maintainers: update Cavium email ids Following Marvell's acquisition of Cavium, we need to update all the Cavium maintainer's entries to point to our new e-mail addresses. Update maintainers as they are no longer working for Cavium. Thanks to Harish Patil for his support and development of our various dpdk drivers. Signed-off-by: Jerin Jacob <jerinj@marvell.com>
2018-12-16 15:43:25 +00:00
M: Anoob Joseph <anoobj@marvell.com>
crypto/octeontx: add PMD skeleton Adding OCTEON TX crypto PMD skeleton. Updating the maintainers files to claim responsibility. Also enabling driver by default by adding the component in common_base. Signed-off-by: Ankur Dwivedi <ankur.dwivedi@caviumnetworks.com> Signed-off-by: Anoob Joseph <anoob.joseph@caviumnetworks.com> Signed-off-by: Murthy NSSR <nidadavolu.murthy@caviumnetworks.com> Signed-off-by: Nithin Dabilpuram <nithin.dabilpuram@caviumnetworks.com> Signed-off-by: Ragothaman Jayaraman <rjayaraman@caviumnetworks.com> Signed-off-by: Srisivasubramanian S <ssrinivasan@caviumnetworks.com> Signed-off-by: Tejasree Kondoj <kondoj.tejasree@caviumnetworks.com>
2018-10-09 09:07:34 +00:00
F: drivers/common/cpt/
F: drivers/crypto/octeontx/
doc: add OCTEON TX crypto guide Adding feature file and guide for OCTEON TX crypto PMD Signed-off-by: Ankur Dwivedi <ankur.dwivedi@caviumnetworks.com> Signed-off-by: Anoob Joseph <anoob.joseph@caviumnetworks.com> Signed-off-by: Murthy NSSR <nidadavolu.murthy@caviumnetworks.com> Signed-off-by: Nithin Dabilpuram <nithin.dabilpuram@caviumnetworks.com> Signed-off-by: Ragothaman Jayaraman <rjayaraman@caviumnetworks.com> Signed-off-by: Srisivasubramanian S <ssrinivasan@caviumnetworks.com> Signed-off-by: Tejasree Kondoj <kondoj.tejasree@caviumnetworks.com>
2018-10-09 09:07:56 +00:00
F: doc/guides/cryptodevs/octeontx.rst
F: doc/guides/cryptodevs/features/octeontx.ini
crypto/octeontx: add PMD skeleton Adding OCTEON TX crypto PMD skeleton. Updating the maintainers files to claim responsibility. Also enabling driver by default by adding the component in common_base. Signed-off-by: Ankur Dwivedi <ankur.dwivedi@caviumnetworks.com> Signed-off-by: Anoob Joseph <anoob.joseph@caviumnetworks.com> Signed-off-by: Murthy NSSR <nidadavolu.murthy@caviumnetworks.com> Signed-off-by: Nithin Dabilpuram <nithin.dabilpuram@caviumnetworks.com> Signed-off-by: Ragothaman Jayaraman <rjayaraman@caviumnetworks.com> Signed-off-by: Srisivasubramanian S <ssrinivasan@caviumnetworks.com> Signed-off-by: Tejasree Kondoj <kondoj.tejasree@caviumnetworks.com>
2018-10-09 09:07:34 +00:00
maintainers: sort crypto drivers list In order to improve consistency, the list of crypto drivers are sorted alphabetically and the word PMD is removed from their names. Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-10-13 13:52:08 +00:00
Crypto Scheduler
M: Fan Zhang <roy.fan.zhang@intel.com>
F: drivers/crypto/scheduler/
F: doc/guides/cryptodevs/scheduler.rst
Intel AES-NI GCM
aesni_gcm: add driver for AES-GCM crypto operations This patch provides the implementation of an AES-NI accelerated crypto PMD which is dependent on Intel's multi-buffer library, see the white paper "Fast Multi-buffer IPsec Implementations on Intel® Architecture Processors" This PMD supports AES_GCM authenticated encryption and authenticated decryption using 128-bit AES keys The patch also contains the related unit tests functions Signed-off-by: Declan Doherty <declan.doherty@intel.com> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Acked-by: John Griffin <john.griffin@intel.com>
2016-03-10 16:41:46 +00:00
M: Declan Doherty <declan.doherty@intel.com>
maintainers: update AESNI MB and GCM PMDs Added myself as co-maintainer of these PMDs, as I am currently working on the library used in these PMDs. Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2019-09-11 09:10:30 +00:00
M: Pablo de Lara <pablo.de.lara.guarch@intel.com>
aesni_gcm: add driver for AES-GCM crypto operations This patch provides the implementation of an AES-NI accelerated crypto PMD which is dependent on Intel's multi-buffer library, see the white paper "Fast Multi-buffer IPsec Implementations on Intel® Architecture Processors" This PMD supports AES_GCM authenticated encryption and authenticated decryption using 128-bit AES keys The patch also contains the related unit tests functions Signed-off-by: Declan Doherty <declan.doherty@intel.com> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Acked-by: John Griffin <john.griffin@intel.com>
2016-03-10 16:41:46 +00:00
F: drivers/crypto/aesni_gcm/
F: doc/guides/cryptodevs/aesni_gcm.rst
maintainers: add drivers features files Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-05-10 13:33:50 +00:00
F: doc/guides/cryptodevs/features/aesni_gcm.ini
aesni_gcm: add driver for AES-GCM crypto operations This patch provides the implementation of an AES-NI accelerated crypto PMD which is dependent on Intel's multi-buffer library, see the white paper "Fast Multi-buffer IPsec Implementations on Intel® Architecture Processors" This PMD supports AES_GCM authenticated encryption and authenticated decryption using 128-bit AES keys The patch also contains the related unit tests functions Signed-off-by: Declan Doherty <declan.doherty@intel.com> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Acked-by: John Griffin <john.griffin@intel.com>
2016-03-10 16:41:46 +00:00
aesni_mb: add driver for multi buffer based crypto This patch provides the initial implementation of the AES-NI multi-buffer based crypto poll mode driver using DPDK's new cryptodev framework. This PMD is dependent on Intel's multibuffer library, see the whitepaper "Fast Multi-buffer IPsec Implementations on Intel® Architecture Processors", see ref 1 for details on the library's design and ref 2 to download the library itself. This initial implementation is limited to supporting the chained operations of "hash then cipher" or "cipher then hash" for the following cipher and hash algorithms: Cipher algorithms: - RTE_CRYPTO_CIPHER_AES_CBC (with 128-bit, 192-bit and 256-bit keys supported) Authentication algorithms: - RTE_CRYPTO_AUTH_SHA1_HMAC - RTE_CRYPTO_AUTH_SHA256_HMAC - RTE_CRYPTO_AUTH_SHA512_HMAC - RTE_CRYPTO_AUTH_AES_XCBC_MAC Important Note: Due to the fact that the multi-buffer library is designed for accelerating IPsec crypto operation, the digest's generated for the HMAC functions are truncated to lengths specified by IPsec RFC's, ie RFC2404 for using HMAC-SHA-1 with IPsec specifies that the digest is truncate from 20 to 12 bytes. Build instructions: To build DPDK with the AESNI_MB_PMD the user is required to download (ref 2) and compile the multi-buffer library on there system before building DPDK. The environmental variable AESNI_MULTI_BUFFER_LIB_PATH must be exported with the path where you extracted and built the multi buffer library and finally set CONFIG_RTE_LIBRTE_PMD_AESNI_MB=y in config/common_linuxapp. Current status: It's doesn't support crypto operation across chained mbufs, or cipher only or hash only operations. ref 1: https://www-ssl.intel.com/content/www/us/en/intelligent-systems/intel-technology/fast-multi-buffer-ipsec-implementations-ia-processors-p ref 2: https://downloadcenter.intel.com/download/22972 Signed-off-by: Declan Doherty <declan.doherty@intel.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-11-25 13:25:15 +00:00
Intel AES-NI Multi-Buffer
M: Declan Doherty <declan.doherty@intel.com>
maintainers: update AESNI MB and GCM PMDs Added myself as co-maintainer of these PMDs, as I am currently working on the library used in these PMDs. Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2019-09-11 09:10:30 +00:00
M: Pablo de Lara <pablo.de.lara.guarch@intel.com>
aesni_mb: add driver for multi buffer based crypto This patch provides the initial implementation of the AES-NI multi-buffer based crypto poll mode driver using DPDK's new cryptodev framework. This PMD is dependent on Intel's multibuffer library, see the whitepaper "Fast Multi-buffer IPsec Implementations on Intel® Architecture Processors", see ref 1 for details on the library's design and ref 2 to download the library itself. This initial implementation is limited to supporting the chained operations of "hash then cipher" or "cipher then hash" for the following cipher and hash algorithms: Cipher algorithms: - RTE_CRYPTO_CIPHER_AES_CBC (with 128-bit, 192-bit and 256-bit keys supported) Authentication algorithms: - RTE_CRYPTO_AUTH_SHA1_HMAC - RTE_CRYPTO_AUTH_SHA256_HMAC - RTE_CRYPTO_AUTH_SHA512_HMAC - RTE_CRYPTO_AUTH_AES_XCBC_MAC Important Note: Due to the fact that the multi-buffer library is designed for accelerating IPsec crypto operation, the digest's generated for the HMAC functions are truncated to lengths specified by IPsec RFC's, ie RFC2404 for using HMAC-SHA-1 with IPsec specifies that the digest is truncate from 20 to 12 bytes. Build instructions: To build DPDK with the AESNI_MB_PMD the user is required to download (ref 2) and compile the multi-buffer library on there system before building DPDK. The environmental variable AESNI_MULTI_BUFFER_LIB_PATH must be exported with the path where you extracted and built the multi buffer library and finally set CONFIG_RTE_LIBRTE_PMD_AESNI_MB=y in config/common_linuxapp. Current status: It's doesn't support crypto operation across chained mbufs, or cipher only or hash only operations. ref 1: https://www-ssl.intel.com/content/www/us/en/intelligent-systems/intel-technology/fast-multi-buffer-ipsec-implementations-ia-processors-p ref 2: https://downloadcenter.intel.com/download/22972 Signed-off-by: Declan Doherty <declan.doherty@intel.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-11-25 13:25:15 +00:00
F: drivers/crypto/aesni_mb/
maintainers: add doc for crypto devices Fixes: 1703e94ac5ce ("qat: add driver for QuickAssist devices") Fixes: 924e84f87306 ("aesni_mb: add driver for multi buffer based crypto") Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2016-03-10 22:35:37 +00:00
F: doc/guides/cryptodevs/aesni_mb.rst
maintainers: add drivers features files Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-05-10 13:33:50 +00:00
F: doc/guides/cryptodevs/features/aesni_mb.ini
aesni_mb: add driver for multi buffer based crypto This patch provides the initial implementation of the AES-NI multi-buffer based crypto poll mode driver using DPDK's new cryptodev framework. This PMD is dependent on Intel's multibuffer library, see the whitepaper "Fast Multi-buffer IPsec Implementations on Intel® Architecture Processors", see ref 1 for details on the library's design and ref 2 to download the library itself. This initial implementation is limited to supporting the chained operations of "hash then cipher" or "cipher then hash" for the following cipher and hash algorithms: Cipher algorithms: - RTE_CRYPTO_CIPHER_AES_CBC (with 128-bit, 192-bit and 256-bit keys supported) Authentication algorithms: - RTE_CRYPTO_AUTH_SHA1_HMAC - RTE_CRYPTO_AUTH_SHA256_HMAC - RTE_CRYPTO_AUTH_SHA512_HMAC - RTE_CRYPTO_AUTH_AES_XCBC_MAC Important Note: Due to the fact that the multi-buffer library is designed for accelerating IPsec crypto operation, the digest's generated for the HMAC functions are truncated to lengths specified by IPsec RFC's, ie RFC2404 for using HMAC-SHA-1 with IPsec specifies that the digest is truncate from 20 to 12 bytes. Build instructions: To build DPDK with the AESNI_MB_PMD the user is required to download (ref 2) and compile the multi-buffer library on there system before building DPDK. The environmental variable AESNI_MULTI_BUFFER_LIB_PATH must be exported with the path where you extracted and built the multi buffer library and finally set CONFIG_RTE_LIBRTE_PMD_AESNI_MB=y in config/common_linuxapp. Current status: It's doesn't support crypto operation across chained mbufs, or cipher only or hash only operations. ref 1: https://www-ssl.intel.com/content/www/us/en/intelligent-systems/intel-technology/fast-multi-buffer-ipsec-implementations-ia-processors-p ref 2: https://downloadcenter.intel.com/download/22972 Signed-off-by: Declan Doherty <declan.doherty@intel.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-11-25 13:25:15 +00:00
qat: add driver for QuickAssist devices This patch adds a PMD for the Intel Quick Assist Technology DH895xxC hardware accelerator. This patch depends on a QAT PF driver for device initialization. See the file docs/guides/cryptodevs/qat.rst for configuration details This patch supports a limited subset of QAT device functionality, currently supporting chaining of cipher and hash operations for the following algorithmsd: Cipher algorithms: - RTE_CRYPTO_CIPHER_AES_CBC (with 128-bit, 192-bit and 256-bit keys supported) Hash algorithms: - RTE_CRYPTO_AUTH_SHA1_HMAC - RTE_CRYPTO_AUTH_SHA256_HMAC - RTE_CRYPTO_AUTH_SHA512_HMAC - RTE_CRYPTO_AUTH_AES_XCBC_MAC Some limitation on this patchset which shall be contributed in a subsequent release: - Chained mbufs are not supported. - Hash only is not supported. - Cipher only is not supported. - Only in-place is currently supported (destination address is the same as source address). - Only supports session-oriented API implementation (session-less APIs are not supported). Signed-off-by: Declan Doherty <declan.doherty@intel.com> Signed-off-by: John Griffin <john.griffin@intel.com> Signed-off-by: Des O Dea <des.j.o.dea@intel.com> Signed-off-by: Fiona Trahe <fiona.trahe@intel.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-11-25 13:25:14 +00:00
Intel QuickAssist
maintainers: claim responsibility for Intel QuickAssist PMD Signed-off-by: Fiona Trahe <fiona.trahe@intel.com> Acked-by: John Griffin <john.griffin@intel.com> Acked-by: Deepak Kumar Jain <deepak.k.jain@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2016-02-05 16:36:01 +00:00
M: John Griffin <john.griffin@intel.com>
M: Fiona Trahe <fiona.trahe@intel.com>
M: Deepak Kumar Jain <deepak.k.jain@intel.com>
qat: add driver for QuickAssist devices This patch adds a PMD for the Intel Quick Assist Technology DH895xxC hardware accelerator. This patch depends on a QAT PF driver for device initialization. See the file docs/guides/cryptodevs/qat.rst for configuration details This patch supports a limited subset of QAT device functionality, currently supporting chaining of cipher and hash operations for the following algorithmsd: Cipher algorithms: - RTE_CRYPTO_CIPHER_AES_CBC (with 128-bit, 192-bit and 256-bit keys supported) Hash algorithms: - RTE_CRYPTO_AUTH_SHA1_HMAC - RTE_CRYPTO_AUTH_SHA256_HMAC - RTE_CRYPTO_AUTH_SHA512_HMAC - RTE_CRYPTO_AUTH_AES_XCBC_MAC Some limitation on this patchset which shall be contributed in a subsequent release: - Chained mbufs are not supported. - Hash only is not supported. - Cipher only is not supported. - Only in-place is currently supported (destination address is the same as source address). - Only supports session-oriented API implementation (session-less APIs are not supported). Signed-off-by: Declan Doherty <declan.doherty@intel.com> Signed-off-by: John Griffin <john.griffin@intel.com> Signed-off-by: Des O Dea <des.j.o.dea@intel.com> Signed-off-by: Fiona Trahe <fiona.trahe@intel.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-11-25 13:25:14 +00:00
F: drivers/crypto/qat/
crypto/qat: move common qat files to common dir - moved common qat files to common/qat dir. - changed common/qat/Makefile, common/qat/meson.build, drivers/Makefile, crypto/Makefile to add possibility of using new files locations - added README file into crypto/qat to clarify where the build is made from - updated MAINTAINERS file Signed-off-by: Tomasz Jozwiak <tomaszx.jozwiak@intel.com> Acked-by: Fiona Trahe <fiona.trahe@intel.com>
2018-07-02 09:39:13 +00:00
F: drivers/common/qat/
maintainers: add doc for crypto devices Fixes: 1703e94ac5ce ("qat: add driver for QuickAssist devices") Fixes: 924e84f87306 ("aesni_mb: add driver for multi buffer based crypto") Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2016-03-10 22:35:37 +00:00
F: doc/guides/cryptodevs/qat.rst
maintainers: add drivers features files Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-05-10 13:33:50 +00:00
F: doc/guides/cryptodevs/features/qat.ini
qat: add driver for QuickAssist devices This patch adds a PMD for the Intel Quick Assist Technology DH895xxC hardware accelerator. This patch depends on a QAT PF driver for device initialization. See the file docs/guides/cryptodevs/qat.rst for configuration details This patch supports a limited subset of QAT device functionality, currently supporting chaining of cipher and hash operations for the following algorithmsd: Cipher algorithms: - RTE_CRYPTO_CIPHER_AES_CBC (with 128-bit, 192-bit and 256-bit keys supported) Hash algorithms: - RTE_CRYPTO_AUTH_SHA1_HMAC - RTE_CRYPTO_AUTH_SHA256_HMAC - RTE_CRYPTO_AUTH_SHA512_HMAC - RTE_CRYPTO_AUTH_AES_XCBC_MAC Some limitation on this patchset which shall be contributed in a subsequent release: - Chained mbufs are not supported. - Hash only is not supported. - Cipher only is not supported. - Only in-place is currently supported (destination address is the same as source address). - Only supports session-oriented API implementation (session-less APIs are not supported). Signed-off-by: Declan Doherty <declan.doherty@intel.com> Signed-off-by: John Griffin <john.griffin@intel.com> Signed-off-by: Des O Dea <des.j.o.dea@intel.com> Signed-off-by: Fiona Trahe <fiona.trahe@intel.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-11-25 13:25:14 +00:00
maintainers: sort crypto drivers list In order to improve consistency, the list of crypto drivers are sorted alphabetically and the word PMD is removed from their names. Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-10-13 13:52:08 +00:00
KASUMI
M: Pablo de Lara <pablo.de.lara.guarch@intel.com>
F: drivers/crypto/kasumi/
F: doc/guides/cryptodevs/kasumi.rst
F: doc/guides/cryptodevs/features/kasumi.ini
maintainers: update Marvell PMDs Natalie and Dmitri are no longer involved in PMDs maintenance hence update the list. Also append new active maintainers to the list. Signed-off-by: Liron Himi <lironh@marvell.com> Acked-by: Tomasz Duszynski <tdu@semihalf.com>
2019-02-20 15:01:59 +00:00
Marvell mvsam
maintainers: update Marvell PMDs Alan is no longer involved in PMDs maintenance hence update the list. Also append new active maintainer to the list. Signed-off-by: Liron Himi <lironh@marvell.com> Acked-by: Tomasz Duszynski <tdu@semihalf.com>
2019-05-20 16:35:12 +00:00
M: Michael Shamis <michaelsh@marvell.com>
maintainers: update Marvell PMDs Natalie and Dmitri are no longer involved in PMDs maintenance hence update the list. Also append new active maintainers to the list. Signed-off-by: Liron Himi <lironh@marvell.com> Acked-by: Tomasz Duszynski <tdu@semihalf.com>
2019-02-20 15:01:59 +00:00
M: Liron Himi <lironh@marvell.com>
crypto/mrvl: rename PMD to mvsam Picking a company stock ticker for a PMD name might not be a best approach in a long run since name is too generic. This patch addresses that and renames mrvl to mvsam. Signed-off-by: Natalie Samsonov <nsamsono@marvell.com> Signed-off-by: Tomasz Duszynski <tdu@semihalf.com>
2018-05-08 08:14:04 +00:00
F: drivers/crypto/mvsam/
F: doc/guides/cryptodevs/mvsam.rst
F: doc/guides/cryptodevs/features/mvsam.ini
crypto/mrvl: add mrvl crypto driver Add support for the Marvell Security Crypto Accelerator EIP197. Driver is based on external, publicly available, Marvell MUSDK library that provides access to the hardware with minimum overhead and high performance. Driver comes with support for the following features: * Symmetric crypto * Sym operation chaining * AES CBC (128) * AES CBC (192) * AES CBC (256) * AES CTR (128) * AES CTR (192) * AES CTR (256) * 3DES CBC * 3DES CTR * MD5 * MD5 HMAC * SHA1 * SHA1 HMAC * SHA256 * SHA256 HMAC * SHA384 * SHA384 HMAC * SHA512 * SHA512 HMAC * AES GCM (128) Driver was engineered cooperatively by Semihalf and Marvell teams. Semihalf: Jacek Siuda <jck@semihalf.com> Tomasz Duszynski <tdu@semihalf.com> Marvell: Dmitri Epshtein <dima@marvell.com> Natalie Samsonov <nsamsono@marvell.com> Signed-off-by: Jacek Siuda <jck@semihalf.com> Signed-off-by: Tomasz Duszynski <tdu@semihalf.com>
2017-10-10 12:17:19 +00:00
crypto/nitrox: introduce Nitrox driver Add bare minimum Nitrox PMD library which handles pci probe, remove and hardware initialization. Add logs, documentation and update maintainers file. Signed-off-by: Nagadheeraj Rottela <rnagadheeraj@marvell.com> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
2019-10-01 06:41:20 +00:00
Marvell Nitrox
M: Nagadheeraj Rottela <rnagadheeraj@marvell.com>
M: Srikanth Jampala <jsrikanth@marvell.com>
F: drivers/crypto/nitrox/
F: doc/guides/cryptodevs/nitrox.rst
F: doc/guides/cryptodevs/features/nitrox.ini
crypto/octeontx2: add PMD skeleton Adding OCTEON TX2 crypto PMD skeleton. Enabling the driver by default in common_base. Signed-off-by: Ankur Dwivedi <adwivedi@marvell.com> Signed-off-by: Anoob Joseph <anoobj@marvell.com> Signed-off-by: Tejasree Kondoj <ktejasree@marvell.com> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
2019-10-16 15:25:34 +00:00
Marvell OCTEON TX2 crypto
M: Ankur Dwivedi <adwivedi@marvell.com>
M: Anoob Joseph <anoobj@marvell.com>
F: drivers/crypto/octeontx2/
F: doc/guides/cryptodevs/octeontx2.rst
F: doc/guides/cryptodevs/features/octeontx2.ini
maintainers: sort crypto drivers list In order to improve consistency, the list of crypto drivers are sorted alphabetically and the word PMD is removed from their names. Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-10-13 13:52:08 +00:00
Null Crypto
M: Declan Doherty <declan.doherty@intel.com>
F: drivers/crypto/null/
F: doc/guides/cryptodevs/null.rst
F: doc/guides/cryptodevs/features/null.ini
crypto/caam_jr: introduce basic driver The caam_jr poll mode crypto driver is supported for NXP SEC 4.x+ (CAAM) hardware accelerator. This driver is by default supported on LE platforms, if it is used on BE platforms like LS104X, config option CONFIG_RTE_LIBRTE_PMD_CAAM_JR_BE can be enabled. This patch add skeleton for caam jobring driver with probe and uintialisation functions Signed-off-by: Gagandeep Singh <g.singh@nxp.com> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
2018-10-12 14:40:42 +00:00
NXP CAAM JR
M: Gagandeep Singh <g.singh@nxp.com>
M: Hemant Agrawal <hemant.agrawal@nxp.com>
F: drivers/crypto/caam_jr/
doc: add CAAM JR guide add caam jr driver details, supported features and algorithms in the document. release note and MAINTAINERS are also updated. Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
2018-10-16 12:48:57 +00:00
F: doc/guides/cryptodevs/caam_jr.rst
F: doc/guides/cryptodevs/features/caam_jr.ini
crypto/caam_jr: introduce basic driver The caam_jr poll mode crypto driver is supported for NXP SEC 4.x+ (CAAM) hardware accelerator. This driver is by default supported on LE platforms, if it is used on BE platforms like LS104X, config option CONFIG_RTE_LIBRTE_PMD_CAAM_JR_BE can be enabled. This patch add skeleton for caam jobring driver with probe and uintialisation functions Signed-off-by: Gagandeep Singh <g.singh@nxp.com> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
2018-10-12 14:40:42 +00:00
crypto/dpaa_sec: add crypto driver for NXP DPAA platform Signed-off-by: Forrest Shi <xuelin.shi@nxp.com> Signed-off-by: Akhil Goyal <akhil.goyal@nxp.com> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
2017-10-09 14:21:40 +00:00
NXP DPAA_SEC
M: Akhil Goyal <akhil.goyal@nxp.com>
M: Hemant Agrawal <hemant.agrawal@nxp.com>
F: drivers/crypto/dpaa_sec/
doc: add NXP DPAA SEC Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com> Signed-off-by: Akhil Goyal <akhil.goyal@nxp.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2017-10-09 14:21:42 +00:00
F: doc/guides/cryptodevs/dpaa_sec.rst
F: doc/guides/cryptodevs/features/dpaa_sec.ini
crypto/dpaa_sec: add crypto driver for NXP DPAA platform Signed-off-by: Forrest Shi <xuelin.shi@nxp.com> Signed-off-by: Akhil Goyal <akhil.goyal@nxp.com> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
2017-10-09 14:21:40 +00:00
crypto/dpaa2_sec: introduce poll mode driver Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com> Signed-off-by: Akhil Goyal <akhil.goyal@nxp.com>
2017-04-20 05:44:16 +00:00
NXP DPAA2_SEC
M: Akhil Goyal <akhil.goyal@nxp.com>
M: Hemant Agrawal <hemant.agrawal@nxp.com>
F: drivers/crypto/dpaa2_sec/
doc: add NXP DPAA2 SEC Signed-off-by: Akhil Goyal <akhil.goyal@nxp.com> Reviewed-by: Hemant Agrawal <hemant.agrawal@nxp.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2017-04-20 05:44:24 +00:00
F: doc/guides/cryptodevs/dpaa2_sec.rst
maintainers: add drivers features files Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-05-10 13:33:50 +00:00
F: doc/guides/cryptodevs/features/dpaa2_sec.ini
crypto/dpaa2_sec: introduce poll mode driver Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com> Signed-off-by: Akhil Goyal <akhil.goyal@nxp.com>
2017-04-20 05:44:16 +00:00
maintainers: sort crypto drivers list In order to improve consistency, the list of crypto drivers are sorted alphabetically and the word PMD is removed from their names. Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-10-13 13:52:08 +00:00
OpenSSL
M: Declan Doherty <declan.doherty@intel.com>
F: drivers/crypto/openssl/
F: doc/guides/cryptodevs/openssl.rst
F: doc/guides/cryptodevs/features/openssl.ini
SNOW 3G
snow3g: add driver for SNOW 3G library Added new SW PMD which makes use of the libsso SW library, which provides wireless algorithms SNOW 3G UEA2 and UIA2 in software. This PMD supports cipher-only, hash-only and chained operations ("cipher then hash" and "hash then cipher") of the following algorithms: - RTE_CRYPTO_SYM_CIPHER_SNOW3G_UEA2 - RTE_CRYPTO_SYM_AUTH_SNOW3G_UIA2 The SNOW 3G hash and cipher algorithms, which are enabled by this crypto PMD are implemented by Intel's libsso software library. For library download and build instructions, see the documentation included (doc/guides/cryptodevs/snow3g.rst) The patch also contains the related unit tests function to test the PMD supported operations. Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Acked-by: Deepak Kumar Jain <deepak.k.jain@intel.com>
2016-03-10 16:33:12 +00:00
M: Pablo de Lara <pablo.de.lara.guarch@intel.com>
F: drivers/crypto/snow3g/
F: doc/guides/cryptodevs/snow3g.rst
maintainers: add drivers features files Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-05-10 13:33:50 +00:00
F: doc/guides/cryptodevs/features/snow3g.ini
snow3g: add driver for SNOW 3G library Added new SW PMD which makes use of the libsso SW library, which provides wireless algorithms SNOW 3G UEA2 and UIA2 in software. This PMD supports cipher-only, hash-only and chained operations ("cipher then hash" and "hash then cipher") of the following algorithms: - RTE_CRYPTO_SYM_CIPHER_SNOW3G_UEA2 - RTE_CRYPTO_SYM_AUTH_SNOW3G_UIA2 The SNOW 3G hash and cipher algorithms, which are enabled by this crypto PMD are implemented by Intel's libsso software library. For library download and build instructions, see the documentation included (doc/guides/cryptodevs/snow3g.rst) The patch also contains the related unit tests function to test the PMD supported operations. Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Acked-by: Deepak Kumar Jain <deepak.k.jain@intel.com>
2016-03-10 16:33:12 +00:00
crypto/virtio: add virtio crypto PMD The virtio crypto device is a virtual cryptography device as well as a kind of virtual hardware accelerator for virtual machines. The linux kernel virtio-crypto driver has been merged, and this patch introduces virtio crypto PMD to achieve better performance. Signed-off-by: Jay Zhou <jianjay.zhou@huawei.com> Reviewed-by: Fan Zhang <roy.fan.zhang@intel.com>
2018-04-17 09:23:17 +00:00
Virtio
M: Jay Zhou <jianjay.zhou@huawei.com>
F: drivers/crypto/virtio/
doc: add virtio crypto PMD guide This patch adds the guide for virtio crypto PMD. Signed-off-by: Jay Zhou <jianjay.zhou@huawei.com> Reviewed-by: Fan Zhang <roy.fan.zhang@intel.com>
2018-04-17 09:23:26 +00:00
F: doc/guides/cryptodevs/virtio.rst
F: doc/guides/cryptodevs/features/virtio.ini
crypto/virtio: add virtio crypto PMD The virtio crypto device is a virtual cryptography device as well as a kind of virtual hardware accelerator for virtual machines. The linux kernel virtio-crypto driver has been merged, and this patch introduces virtio crypto PMD to achieve better performance. Signed-off-by: Jay Zhou <jianjay.zhou@huawei.com> Reviewed-by: Fan Zhang <roy.fan.zhang@intel.com>
2018-04-17 09:23:17 +00:00
maintainers: sort crypto drivers list In order to improve consistency, the list of crypto drivers are sorted alphabetically and the word PMD is removed from their names. Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-10-13 13:52:08 +00:00
ZUC
crypto/zuc: add driver for ZUC library Added new SW PMD which makes use of the libsso SW library, which provides wireless algorithms ZUC EEA3 and EIA3 in software. This PMD supports cipher-only, hash-only and chained operations ("cipher then hash" and "hash then cipher") of the following algorithms: - RTE_CRYPTO_SYM_CIPHER_ZUC_EEA3 - RTE_CRYPTO_SYM_AUTH_ZUC_EIA3 The ZUC hash and cipher algorithms, which are enabled by this crypto PMD are implemented by Intel's libsso software library. Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Acked-by: Deepak Kumar Jain <deepak.k.jain@intel.com>
2016-09-29 02:59:47 +00:00
M: Pablo de Lara <pablo.de.lara.guarch@intel.com>
F: drivers/crypto/zuc/
F: doc/guides/cryptodevs/zuc.rst
maintainers: add drivers features files Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-05-10 13:33:50 +00:00
F: doc/guides/cryptodevs/features/zuc.ini
crypto/zuc: add driver for ZUC library Added new SW PMD which makes use of the libsso SW library, which provides wireless algorithms ZUC EEA3 and EIA3 in software. This PMD supports cipher-only, hash-only and chained operations ("cipher then hash" and "hash then cipher") of the following algorithms: - RTE_CRYPTO_SYM_CIPHER_ZUC_EEA3 - RTE_CRYPTO_SYM_AUTH_ZUC_EIA3 The ZUC hash and cipher algorithms, which are enabled by this crypto PMD are implemented by Intel's libsso software library. Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Acked-by: Deepak Kumar Jain <deepak.k.jain@intel.com>
2016-09-29 02:59:47 +00:00
event/dpaa2: add basic build infrastructure Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2017-06-30 08:54:16 +00:00
compress/isal: add skeleton ISA-L compression PMD Adding basic skeleton of the ISA-L compression driver. No compression functionality, but lays the foundation for operations in the rest of the patchset. The ISA-L compression driver utilizes Intel's ISA-L compression library and compressdev API. Signed-off-by: Lee Daly <lee.daly@intel.com> Reviewed-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2018-05-09 16:14:26 +00:00
Compression Drivers
-------------------
T: git://dpdk.org/next/dpdk-next-crypto
use registered name for OCTEON TX references 'OCTEON TX' is the registered name. All other usages need to be fixed. Signed-off-by: Anoob Joseph <anoob.joseph@caviumnetworks.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2018-10-10 02:50:56 +00:00
Cavium OCTEON TX zipvf
maintainers: update Cavium email ids Following Marvell's acquisition of Cavium, we need to update all the Cavium maintainer's entries to point to our new e-mail addresses. Update maintainers as they are no longer working for Cavium. Thanks to Harish Patil for his support and development of our various dpdk drivers. Signed-off-by: Jerin Jacob <jerinj@marvell.com>
2018-12-16 15:43:25 +00:00
M: Ashish Gupta <ashish.gupta@marvell.com>
compress/octeontx: introduce octeontx zip PMD Octentx zipvf PMD provides hardware acceleration for deflate and lzs compression and decompression operations using Octeontx zip co-processor, which provide 8 virtualized zip devices. This patch add basic initialization routine to register zip VFs to compressdev library. Signed-off-by: Ashish Gupta <ashish.gupta@caviumnetworks.com> Signed-off-by: Shally Verma <shally.verma@caviumnetworks.com> Signed-off-by: Sunila Sahu <sunila.sahu@caviumnetworks.com>
2018-07-25 17:04:51 +00:00
F: drivers/compress/octeontx/
doc: add octeonx zip guide Add Octeontx ZIP PMD feature specification and user guide with build and run instructions. Signed-off-by: Ashish Gupta <ashish.gupta@caviumnetworks.com> Signed-off-by: Shally Verma <shally.verma@caviumnetworks.com> Signed-off-by: Sunila Sahu <sunila.sahu@caviumnetworks.com>
2018-07-25 17:04:55 +00:00
F: doc/guides/compressdevs/octeontx.rst
F: doc/guides/compressdevs/features/octeontx.ini
compress/octeontx: introduce octeontx zip PMD Octentx zipvf PMD provides hardware acceleration for deflate and lzs compression and decompression operations using Octeontx zip co-processor, which provide 8 virtualized zip devices. This patch add basic initialization routine to register zip VFs to compressdev library. Signed-off-by: Ashish Gupta <ashish.gupta@caviumnetworks.com> Signed-off-by: Shally Verma <shally.verma@caviumnetworks.com> Signed-off-by: Sunila Sahu <sunila.sahu@caviumnetworks.com>
2018-07-25 17:04:51 +00:00
compress/qat: add empty driver Add Makefiles, meson files, and empty source files for compression PMD. Handle cases for building either symmetric crypto PMD or compression PMD or both and the common files both depend on. Signed-off-by: Fiona Trahe <fiona.trahe@intel.com> Signed-off-by: Tomasz Jozwiak <tomaszx.jozwiak@intel.com>
2018-07-13 02:28:11 +00:00
Intel QuickAssist
M: Fiona Trahe <fiona.trahe@intel.com>
F: drivers/compress/qat/
F: drivers/common/qat/
compress/isal: add skeleton ISA-L compression PMD Adding basic skeleton of the ISA-L compression driver. No compression functionality, but lays the foundation for operations in the rest of the patchset. The ISA-L compression driver utilizes Intel's ISA-L compression library and compressdev API. Signed-off-by: Lee Daly <lee.daly@intel.com> Reviewed-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2018-05-09 16:14:26 +00:00
ISA-L
M: Lee Daly <lee.daly@intel.com>
F: drivers/compress/isal/
doc: add compression driver and ISA-L PMD guides This adds general compression drivers feature guide as well as the ISA-L PMD documentation and guide. Signed-off-by: Lee Daly <lee.daly@intel.com> Reviewed-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2018-05-09 16:14:35 +00:00
F: doc/guides/compressdevs/isal.rst
F: doc/guides/compressdevs/features/isal.ini
compress/isal: add skeleton ISA-L compression PMD Adding basic skeleton of the ISA-L compression driver. No compression functionality, but lays the foundation for operations in the rest of the patchset. The ISA-L compression driver utilizes Intel's ISA-L compression library and compressdev API. Signed-off-by: Lee Daly <lee.daly@intel.com> Reviewed-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2018-05-09 16:14:26 +00:00
compress/zlib: introduce zlib PMD Add initial PMD setup routines in compressdev framework. ZLIB PMD appears as virtual compression device. User would need to install zlib prior to enabling this PMD. Signed-off-by: Sunila Sahu <sunila.sahu@caviumnetworks.com> Signed-off-by: Shally Verma <shally.verma@caviumnetworks.com> Signed-off-by: Ashish Gupta <ashish.gupta@caviumnetworks.com>
2018-07-24 15:05:32 +00:00
ZLIB
maintainers: update Cavium email ids Following Marvell's acquisition of Cavium, we need to update all the Cavium maintainer's entries to point to our new e-mail addresses. Update maintainers as they are no longer working for Cavium. Thanks to Harish Patil for his support and development of our various dpdk drivers. Signed-off-by: Jerin Jacob <jerinj@marvell.com>
2018-12-16 15:43:25 +00:00
M: Sunila Sahu <ssahu@marvell.com>
compress/zlib: introduce zlib PMD Add initial PMD setup routines in compressdev framework. ZLIB PMD appears as virtual compression device. User would need to install zlib prior to enabling this PMD. Signed-off-by: Sunila Sahu <sunila.sahu@caviumnetworks.com> Signed-off-by: Shally Verma <shally.verma@caviumnetworks.com> Signed-off-by: Ashish Gupta <ashish.gupta@caviumnetworks.com>
2018-07-24 15:05:32 +00:00
F: drivers/compress/zlib/
doc: add zlib PMD guide Add zlib pmd feature support and user guide with build and run instructions Signed-off-by: Sunila Sahu <sunila.sahu@caviumnetworks.com> Signed-off-by: Shally Verma <shally.verma@caviumnetworks.com> Signed-off-by: Ashish Gupta <ashish.gupta@caviumnetworks.com>
2018-07-24 15:05:36 +00:00
F: doc/guides/compressdevs/zlib.rst
F: doc/guides/compressdevs/features/zlib.ini
compress/zlib: introduce zlib PMD Add initial PMD setup routines in compressdev framework. ZLIB PMD appears as virtual compression device. User would need to install zlib prior to enabling this PMD. Signed-off-by: Sunila Sahu <sunila.sahu@caviumnetworks.com> Signed-off-by: Shally Verma <shally.verma@caviumnetworks.com> Signed-off-by: Ashish Gupta <ashish.gupta@caviumnetworks.com>
2018-07-24 15:05:32 +00:00
compress/isal: add skeleton ISA-L compression PMD Adding basic skeleton of the ISA-L compression driver. No compression functionality, but lays the foundation for operations in the rest of the patchset. The ISA-L compression driver utilizes Intel's ISA-L compression library and compressdev API. Signed-off-by: Lee Daly <lee.daly@intel.com> Reviewed-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2018-05-09 16:14:26 +00:00
drivers: introduce vDPA class The vDPA (vhost data path acceleration) drivers provide support for the vDPA operations introduced by the rte_vhost library. Any driver which provides the vDPA operations should be moved\added to the vdpa class under drivers/vdpa/. Create the general files for vDPA class in drivers and in documentation. The management tree for vDPA drivers is git://dpdk.org/next/dpdk-next-virtio. Signed-off-by: Matan Azrad <matan@mellanox.com> Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
2020-01-09 11:00:15 +00:00
vDPA Drivers
------------
T: git://dpdk.org/next/dpdk-next-virtio
drivers: move ifc to vDPA directory A new vDPA class was recently introduced. IFC driver implements the vDPA operations, hence it should be moved to the vDPA class. Move it. Signed-off-by: Matan Azrad <matan@mellanox.com> Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
2020-01-09 11:00:17 +00:00
Intel ifc
M: Xiao Wang <xiao.w.wang@intel.com>
F: drivers/vdpa/ifc/
F: doc/guides/vdpadevs/ifc.rst
F: doc/guides/vdpadevs/features/ifcvf.ini
vdpa/mlx5: introduce Mellanox vDPA driver Add a new driver to support vDPA operations by Mellanox devices. The first Mellanox devices which support vDPA operations are ConnectX-6 Dx and Bluefield1 HCA for their PF ports and VF ports. This driver is depending on rdma-core like the mlx5 PMD, also it is going to use mlx5 DevX to create HW objects directly by the FW. Hence, the common/mlx5 library is linked to the mlx5_vdpa driver. This driver will not be compiled by default due to the above dependencies. Register a new log type for this driver. Signed-off-by: Matan Azrad <matan@mellanox.com> Acked-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com> Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
2020-02-02 16:03:41 +00:00
Mellanox mlx5 vDPA
M: Matan Azrad <matan@mellanox.com>
M: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
F: drivers/vdpa/mlx5/
F: doc/guides/vdpadevs/mlx5.rst
F: doc/guides/vdpadevs/features/mlx5.ini
drivers: introduce vDPA class The vDPA (vhost data path acceleration) drivers provide support for the vDPA operations introduced by the rte_vhost library. Any driver which provides the vDPA operations should be moved\added to the vdpa class under drivers/vdpa/. Create the general files for vDPA class in drivers and in documentation. The management tree for vDPA drivers is git://dpdk.org/next/dpdk-next-virtio. Signed-off-by: Matan Azrad <matan@mellanox.com> Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
2020-01-09 11:00:15 +00:00
maintainers: add eventdev section and claim SW PMD Add a section for the eventdev PMDs, and note the next-tree. Claim maintainership of the software eventdev PMD. Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2017-04-01 10:41:16 +00:00
Eventdev Drivers
----------------
maintainers: update Cavium email ids Following Marvell's acquisition of Cavium, we need to update all the Cavium maintainer's entries to point to our new e-mail addresses. Update maintainers as they are no longer working for Cavium. Thanks to Harish Patil for his support and development of our various dpdk drivers. Signed-off-by: Jerin Jacob <jerinj@marvell.com>
2018-12-16 15:43:25 +00:00
M: Jerin Jacob <jerinj@marvell.com>
maintainers: add eventdev section and claim SW PMD Add a section for the eventdev PMDs, and note the next-tree. Claim maintainership of the software eventdev PMD. Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2017-04-01 10:41:16 +00:00
T: git://dpdk.org/next/dpdk-next-eventdev
use registered name for OCTEON TX references 'OCTEON TX' is the registered name. All other usages need to be fixed. Signed-off-by: Anoob Joseph <anoob.joseph@caviumnetworks.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2018-10-10 02:50:56 +00:00
Cavium OCTEON TX ssovf
maintainers: update Cavium email ids Following Marvell's acquisition of Cavium, we need to update all the Cavium maintainer's entries to point to our new e-mail addresses. Update maintainers as they are no longer working for Cavium. Thanks to Harish Patil for his support and development of our various dpdk drivers. Signed-off-by: Jerin Jacob <jerinj@marvell.com>
2018-12-16 15:43:25 +00:00
M: Jerin Jacob <jerinj@marvell.com>
doc: add OCTEONTX ssovf details Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Signed-off-by: Santosh Shukla <santosh.shukla@caviumnetworks.com> Acked-by: Harry van Haaren <harry.van.haaren@intel.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2017-03-03 17:28:21 +00:00
F: drivers/event/octeontx/
F: doc/guides/eventdevs/octeontx.rst
use registered name for OCTEON TX references 'OCTEON TX' is the registered name. All other usages need to be fixed. Signed-off-by: Anoob Joseph <anoob.joseph@caviumnetworks.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2018-10-10 02:50:56 +00:00
Cavium OCTEON TX timvf
maintainers: update Cavium email ids Following Marvell's acquisition of Cavium, we need to update all the Cavium maintainer's entries to point to our new e-mail addresses. Update maintainers as they are no longer working for Cavium. Thanks to Harish Patil for his support and development of our various dpdk drivers. Signed-off-by: Jerin Jacob <jerinj@marvell.com>
2018-12-16 15:43:25 +00:00
M: Pavan Nikhilesh <pbhagavatula@marvell.com>
event/octeontx: probe timvf PCIe devices On Octeontx HW, each event timer device is enumerated as separate SRIOV VF PCIe device. In order to expose as a event timer device: On PCIe probe, the driver stores the information associated with the PCIe device and later when application requests for a event timer device through `rte_event_timer_adapter_create` the driver infrastructure creates the timer adapter with earlier probed PCIe VF devices. Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2018-04-09 21:00:26 +00:00
F: drivers/event/octeontx/timvf_*
event/octeontx2: add build infra and device probe Add the make and meson based build infrastructure along with the eventdev(SSO) device probe. Signed-off-by: Jerin Jacob <jerinj@marvell.com> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com> Signed-off-by: Nithin Dabilpuram <ndabilpuram@marvell.com>
2019-06-28 18:23:12 +00:00
Marvell OCTEON TX2
M: Pavan Nikhilesh <pbhagavatula@marvell.com>
M: Jerin Jacob <jerinj@marvell.com>
F: drivers/event/octeontx2/
F: doc/guides/eventdevs/octeontx2.rst
event/dpaa: introduce PMD Signed-off-by: Sunil Kumar Kori <sunil.kori@nxp.com> Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
2018-01-16 20:43:58 +00:00
NXP DPAA eventdev
M: Hemant Agrawal <hemant.agrawal@nxp.com>
maintainers: claim maintainership of DPAA eventdev Sunil Kori is no longer with NXP Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
2019-07-15 11:38:29 +00:00
M: Nipun Gupta <nipun.gupta@nxp.com>
event/dpaa: introduce PMD Signed-off-by: Sunil Kumar Kori <sunil.kori@nxp.com> Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
2018-01-16 20:43:58 +00:00
F: drivers/event/dpaa/
doc: add DPAA eventdev guide Signed-off-by: Sunil Kumar Kori <sunil.kori@nxp.com> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2018-01-16 20:44:03 +00:00
F: doc/guides/eventdevs/dpaa.rst
event/dpaa: introduce PMD Signed-off-by: Sunil Kumar Kori <sunil.kori@nxp.com> Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
2018-01-16 20:43:58 +00:00
maintainers: fix typo and ordering Fix logical/alphabetical ordering, spacing, and syntax typo. Fixes: 8fb3b2576025 ("maintainers: call out subtree committers") Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2018-04-23 01:18:35 +00:00
NXP DPAA2 eventdev
M: Hemant Agrawal <hemant.agrawal@nxp.com>
M: Nipun Gupta <nipun.gupta@nxp.com>
F: drivers/event/dpaa2/
F: doc/guides/eventdevs/dpaa2.rst
maintainers: add eventdev section and claim SW PMD Add a section for the eventdev PMDs, and note the next-tree. Claim maintainership of the software eventdev PMD. Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2017-04-01 10:41:16 +00:00
Software Eventdev PMD
M: Harry van Haaren <harry.van.haaren@intel.com>
F: drivers/event/sw/
F: doc/guides/eventdevs/sw.rst
examples/eventdev: rename example Rename eventdev_pipeline_sw_pmd to eventdev_pipeline as it is no longer specific underlying event device. Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com> Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
2018-01-10 11:10:12 +00:00
F: examples/eventdev_pipeline/
F: doc/guides/sample_app_ug/eventdev_pipeline.rst
maintainers: add eventdev section and claim SW PMD Add a section for the eventdev PMDs, and note the next-tree. Claim maintainership of the software eventdev PMD. Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2017-04-01 10:41:16 +00:00
event/dsw: add device registration and build system This patch contains the Meson and GNU Make build system extensions required for the Distributed Event Device, and also the initialization code for the driver itself. Signed-off-by: Mattias Rönnblom <mattias.ronnblom@ericsson.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2018-09-18 12:45:05 +00:00
Distributed Software Eventdev PMD
M: Mattias Rönnblom <mattias.ronnblom@ericsson.com>
F: drivers/event/dsw/
event/dsw: add documentation The DSW event device is documented in DPDK Programmer's Guide. The MAINTAINERS file and the 18.11 release notes are updated. Signed-off-by: Mattias Rönnblom <mattias.ronnblom@ericsson.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2018-09-18 12:45:14 +00:00
F: doc/guides/eventdevs/dsw.rst
event/dsw: add device registration and build system This patch contains the Meson and GNU Make build system extensions required for the Distributed Event Device, and also the initialization code for the driver itself. Signed-off-by: Mattias Rönnblom <mattias.ronnblom@ericsson.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
2018-09-18 12:45:05 +00:00
event/opdl: add OPDL ring infrastructure library OPDL ring is the core infrastructure of OPDL PMD. OPDL ring library provide the core data structure and core helper function set. The Ring implements a single ring multi-port/stage pipelined packet distribution mechanism. This mechanism has the following characteristics: • No multiple queue cost, therefore, latency is significant reduced. • Fixed dependencies between queue/ports is more suitable for complex. fixed pipelines of stateless packet processing (static pipeline). • Has decentralized distribution (no scheduling core). • Packets remain in order (no reorder core(s)). * Update build system to enable compilation. Signed-off-by: Liang Ma <liang.j.ma@intel.com> Signed-off-by: Peter Mccarthy <peter.mccarthy@intel.com> Reviewed-by: Seán Harte <seanbh@gmail.com>
2018-01-09 14:18:50 +00:00
Software OPDL Eventdev PMD
M: Liang Ma <liang.j.ma@intel.com>
M: Peter Mccarthy <peter.mccarthy@intel.com>
F: drivers/event/opdl/
doc: add eventdev OPDL PMD guide Add the description about opdl pmd Signed-off-by: Liang Ma <liang.j.ma@intel.com> Signed-off-by: Peter Mccarthy <peter.mccarthy@intel.com> Acked-by: Marko Kovacevic <marko.kovacevic@intel.com>
2018-01-09 14:19:01 +00:00
F: doc/guides/eventdevs/opdl.rst
event/opdl: add OPDL ring infrastructure library OPDL ring is the core infrastructure of OPDL PMD. OPDL ring library provide the core data structure and core helper function set. The Ring implements a single ring multi-port/stage pipelined packet distribution mechanism. This mechanism has the following characteristics: • No multiple queue cost, therefore, latency is significant reduced. • Fixed dependencies between queue/ports is more suitable for complex. fixed pipelines of stateless packet processing (static pipeline). • Has decentralized distribution (no scheduling core). • Packets remain in order (no reorder core(s)). * Update build system to enable compilation. Signed-off-by: Liang Ma <liang.j.ma@intel.com> Signed-off-by: Peter Mccarthy <peter.mccarthy@intel.com> Reviewed-by: Seán Harte <seanbh@gmail.com>
2018-01-09 14:18:50 +00:00
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
raw/dpaa2_qdma: introduce the DPAA2 QDMA driver DPAA2 QDMA driver uses MC DPDMAI object. This driver enables the user (app) to perform data DMA without involving CPU in the DMA process Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com> Acked-by: Shreyansh Jain <shreyansh.jain@nxp.com>
2018-05-03 16:06:07 +00:00
Rawdev Drivers
--------------
raw/ifpga/base: add Intel FPGA OPAE share code This patch adds Intel FPGA Open Programmable Acceleration Engine (OPAE)[1] base driver code, in order to support Intel FPGA devices under DPDK. The base code currently supports Intel FPGA solutions including integrated solution (Intel(R) Xeon(R) CPU with FPGAs) and discrete solution (Intel(R) Programmable Acceleration Card with Intel(R) Arria(R) 10 FPGA) and it could be extended to support more FPGA devices in the future. Please refer to [1][2] for more introduction on OPAE and Intel FPGAs. [1] https://01.org/OPAE [2] https://www.altera.com/solutions/acceleration-hub/overview.html Signed-off-by: Tianfei Zhang <tianfei.zhang@intel.com> Signed-off-by: Hao Wu <hao.wu@intel.com> Signed-off-by: Yilun Xu <yilun.xu@intel.com> Reviewed-by: Qi Zhang <qi.z.zhang@intel.com>
2018-05-11 08:31:30 +00:00
Intel FPGA
raw/ifpga: add Intel FPGA bus rawdev driver Add Intel FPGA BUS Rawdev Driver which is based on librte_rawdev library. Signed-off-by: Rosen Xu <rosen.xu@intel.com> Signed-off-by: Yanglong Wu <yanglong.wu@intel.com> Signed-off-by: Tianfei Zhang <tianfei.zhang@intel.com> Acked-by: Shreyansh Jain <shreyansh.jain@nxp.com> Reviewed-by: Qi Zhang <qi.z.zhang@intel.com>
2018-05-11 08:31:31 +00:00
M: Rosen Xu <rosen.xu@intel.com>
raw/ifpga/base: add Intel FPGA OPAE share code This patch adds Intel FPGA Open Programmable Acceleration Engine (OPAE)[1] base driver code, in order to support Intel FPGA devices under DPDK. The base code currently supports Intel FPGA solutions including integrated solution (Intel(R) Xeon(R) CPU with FPGAs) and discrete solution (Intel(R) Programmable Acceleration Card with Intel(R) Arria(R) 10 FPGA) and it could be extended to support more FPGA devices in the future. Please refer to [1][2] for more introduction on OPAE and Intel FPGAs. [1] https://01.org/OPAE [2] https://www.altera.com/solutions/acceleration-hub/overview.html Signed-off-by: Tianfei Zhang <tianfei.zhang@intel.com> Signed-off-by: Hao Wu <hao.wu@intel.com> Signed-off-by: Yilun Xu <yilun.xu@intel.com> Reviewed-by: Qi Zhang <qi.z.zhang@intel.com>
2018-05-11 08:31:30 +00:00
M: Tianfei zhang <tianfei.zhang@intel.com>
maintainers: update for ifpga Add raw/ifpga to next-net-intel tree. Signed-off-by: Xiaolong Ye <xiaolong.ye@intel.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2019-10-28 05:47:16 +00:00
T: git://dpdk.org/next/dpdk-next-net-intel
drivers/raw: remove rawdev from directory names The ifpga and skeleton rawdev drivers included "rawdev" in their directory names, which was superfluous given that they were in the drivers/raw directory. Shorten the names via this patch. For meson builds, this will rename the final library .so/.a files produced, but those will be renamed again later via a patch to standardize rawdev names. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
2019-07-05 09:34:00 +00:00
F: drivers/raw/ifpga/
F: doc/guides/rawdevs/ifpga.rst
raw/ifpga/base: add Intel FPGA OPAE share code This patch adds Intel FPGA Open Programmable Acceleration Engine (OPAE)[1] base driver code, in order to support Intel FPGA devices under DPDK. The base code currently supports Intel FPGA solutions including integrated solution (Intel(R) Xeon(R) CPU with FPGAs) and discrete solution (Intel(R) Programmable Acceleration Card with Intel(R) Arria(R) 10 FPGA) and it could be extended to support more FPGA devices in the future. Please refer to [1][2] for more introduction on OPAE and Intel FPGAs. [1] https://01.org/OPAE [2] https://www.altera.com/solutions/acceleration-hub/overview.html Signed-off-by: Tianfei Zhang <tianfei.zhang@intel.com> Signed-off-by: Hao Wu <hao.wu@intel.com> Signed-off-by: Yilun Xu <yilun.xu@intel.com> Reviewed-by: Qi Zhang <qi.z.zhang@intel.com>
2018-05-11 08:31:30 +00:00
raw/ioat: introduce IOAT driver Add stubs for ioat rawdev driver support in DPDK, specifically: * makefile and meson build hooks * initial public header file * rawdev main C file, with probe and release functions * release note update announcing the driver * initial documentation for the new section in the rawdev doc * unit test stubs for device unit tests Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: Anatoly Burakov <anatoly.burakov@intel.com> Acked-by: Jiayu Hu <jiayu.hu@intel.com> Tested-by: Harry van Haaren <harry.van.haaren@intel.com>
2019-07-02 14:12:23 +00:00
IOAT Rawdev
M: Bruce Richardson <bruce.richardson@intel.com>
F: drivers/raw/ioat/
drivers/raw: remove rawdev from directory names The ifpga and skeleton rawdev drivers included "rawdev" in their directory names, which was superfluous given that they were in the drivers/raw directory. Shorten the names via this patch. For meson builds, this will rename the final library .so/.a files produced, but those will be renamed again later via a patch to standardize rawdev names. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
2019-07-05 09:34:00 +00:00
F: doc/guides/rawdevs/ioat.rst
examples/ioat: add new sample app for ioat driver A new sample app demonstrating use of driver for CBDMA. The app receives packets, performs software or hardware copy, changes packets' MAC addresses (if enabled) and forwards them. The change covers ports initialization, closing connection and argument parsing. Signed-off-by: Pawel Modrak <pawelx.modrak@intel.com> Signed-off-by: Marcin Baran <marcinx.baran@intel.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2019-10-07 11:08:04 +00:00
F: examples/ioat/
doc: add IOAT sample app guide Added guide for IOAT sample app usage and code description. Signed-off-by: Marcin Baran <marcinx.baran@intel.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2019-10-07 11:08:09 +00:00
F: doc/guides/sample_app_ug/ioat.rst
raw/ioat: introduce IOAT driver Add stubs for ioat rawdev driver support in DPDK, specifically: * makefile and meson build hooks * initial public header file * rawdev main C file, with probe and release functions * release note update announcing the driver * initial documentation for the new section in the rawdev doc * unit test stubs for device unit tests Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: Anatoly Burakov <anatoly.burakov@intel.com> Acked-by: Jiayu Hu <jiayu.hu@intel.com> Tested-by: Harry van Haaren <harry.van.haaren@intel.com>
2019-07-02 14:12:23 +00:00
raw/dpaa2_qdma: introduce the DPAA2 QDMA driver DPAA2 QDMA driver uses MC DPDMAI object. This driver enables the user (app) to perform data DMA without involving CPU in the DMA process Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com> Acked-by: Shreyansh Jain <shreyansh.jain@nxp.com>
2018-05-03 16:06:07 +00:00
NXP DPAA2 QDMA
M: Nipun Gupta <nipun.gupta@nxp.com>
F: drivers/raw/dpaa2_qdma/
doc: add DPAA2 QDMA rawdev guide Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com> Acked-by: Shreyansh Jain <shreyansh.jain@nxp.com>
2018-05-03 16:06:10 +00:00
F: doc/guides/rawdevs/dpaa2_qdma.rst
raw/dpaa2_qdma: introduce the DPAA2 QDMA driver DPAA2 QDMA driver uses MC DPDMAI object. This driver enables the user (app) to perform data DMA without involving CPU in the DMA process Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com> Acked-by: Shreyansh Jain <shreyansh.jain@nxp.com>
2018-05-03 16:06:07 +00:00
raw/dpaa2_cmdif: introduce DPAA2 command interface driver Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com> Acked-by: Shreyansh Jain <shreyansh.jain@nxp.com>
2018-05-04 10:11:26 +00:00
DPAA2 CMDIF
M: Nipun Gupta <nipun.gupta@nxp.com>
F: drivers/raw/dpaa2_cmdif/
doc: add DPAA2 CMDIF rawdev guide Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com> Acked-by: Marko Kovacevic <marko.kovacevic@intel.com> Acked-by: Shreyansh Jain <shreyansh.jain@nxp.com>
2018-05-04 10:11:29 +00:00
F: doc/guides/rawdevs/dpaa2_cmdif.rst
raw/dpaa2_cmdif: introduce DPAA2 command interface driver Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com> Acked-by: Shreyansh Jain <shreyansh.jain@nxp.com>
2018-05-04 10:11:26 +00:00
raw/octeontx2_dma: add build infra and device probe Add the make and meson based build infrastructure along with the DMA device probe with documentation infrastructure. Signed-off-by: Jerin Jacob <jerinj@marvell.com> Signed-off-by: Satha Rao <skoteshwar@marvell.com> Signed-off-by: Vamsi Attunuru <vattunuru@marvell.com>
2019-07-05 08:37:58 +00:00
Marvell OCTEON TX2 DMA
M: Satha Rao <skoteshwar@marvell.com>
F: drivers/raw/octeontx2_dma/
F: doc/guides/rawdevs/octeontx2_dma.rst
raw/octeontx2_ep: add build infra and device probe Add the OCTEON TX2 SDP EP device probe along with the build infrastructure for Make and meson builds. Signed-off-by: Mahipal Challa <mchalla@marvell.com> Reviewed-by: Gavin Hu <gavin.hu@arm.com>
2020-01-13 06:00:36 +00:00
Marvell OCTEON TX2 EP
M: Mahipal Challa <mchalla@marvell.com>
F: drivers/raw/octeontx2_ep/
F: doc/guides/rawdevs/octeontx2_ep.rst
raw/ntb: introduce NTB raw device driver Introduce rawdev driver support for NTB (Non-transparent Bridge) which can help to connect two separate hosts with each other. Signed-off-by: Xiaoyun Li <xiaoyun.li@intel.com> Acked-by: Jingjing Wu <jingjing.wu@intel.com> Reviewed-by: Xiaolong Ye <xiaolong.ye@intel.com>
2019-07-02 06:25:17 +00:00
NTB
M: Xiaoyun Li <xiaoyun.li@intel.com>
M: Jingjing Wu <jingjing.wu@intel.com>
F: drivers/raw/ntb/
F: doc/guides/rawdevs/ntb.rst
examples/ntb: add example for NTB Enable an example for rawdev ntb. Support interactive mode to send file on one host and receive file from another host. The command line would be 'send [filepath]' and 'receive [filepath]'. But since the FIFO is not enabled right now, use rte_memcpy as the enqueue and dequeue functions and only support transmitting file no more than 4M. Signed-off-by: Xiaoyun Li <xiaoyun.li@intel.com> Acked-by: Jingjing Wu <jingjing.wu@intel.com> Reviewed-by: Xiaolong Ye <xiaolong.ye@intel.com>
2019-07-02 06:25:21 +00:00
F: examples/ntb/
F: doc/guides/sample_app_ug/ntb.rst
raw/ntb: introduce NTB raw device driver Introduce rawdev driver support for NTB (Non-transparent Bridge) which can help to connect two separate hosts with each other. Signed-off-by: Xiaoyun Li <xiaoyun.li@intel.com> Acked-by: Jingjing Wu <jingjing.wu@intel.com> Reviewed-by: Xiaolong Ye <xiaolong.ye@intel.com>
2019-07-02 06:25:17 +00:00
raw/dpaa2_qdma: introduce the DPAA2 QDMA driver DPAA2 QDMA driver uses MC DPDMAI object. This driver enables the user (app) to perform data DMA without involving CPU in the DMA process Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com> Acked-by: Shreyansh Jain <shreyansh.jain@nxp.com>
2018-05-03 16:06:07 +00:00
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
Packet processing
-----------------
Network headers
net: introduce net library Previously, librte_net only contained header files. Add a C file (empty for now) and generate a library. It will contain network helpers like checksum calculation, software packet type parser, ... Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
2016-10-03 08:38:45 +00:00
M: Olivier Matz <olivier.matz@6wind.com>
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: lib/librte_net/
net: add CRC computation API APIs for selecting the architecure specific implementation and computing the crc (16-bit and 32-bit CRCs) are added. For CRCs calculation, scalar as well as x86 intrinsic(sse4.2) versions are implemented. The scalar version is based on generic Look-Up Table(LUT) algorithm, while x86 intrinsic version uses carry-less multiplication for fast CRC computation. Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-04-05 20:49:49 +00:00
Packet CRC
M: Jasvinder Singh <jasvinder.singh@intel.com>
F: lib/librte_net/rte_net_crc*
F: lib/librte_net/net_crc_sse.h
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_crc.c
net: add CRC computation API APIs for selecting the architecure specific implementation and computing the crc (16-bit and 32-bit CRCs) are added. For CRCs calculation, scalar as well as x86 intrinsic(sse4.2) versions are implemented. The scalar version is based on generic Look-Up Table(LUT) algorithm, while x86 intrinsic version uses carry-less multiplication for fast CRC computation. Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-04-05 20:49:49 +00:00
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
IP fragmentation & reassembly
maintainers: claim IP fragmentation and ACL Signed-off-by: Konstantin Ananyev <konstantin.ananyev@intel.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-02-06 12:35:49 +00:00
M: Konstantin Ananyev <konstantin.ananyev@intel.com>
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: lib/librte_ip_frag/
F: doc/guides/prog_guide/ip_fragment_reassembly_lib.rst
test/ipfrag: add unit test case Initial IP fragmentation unit test. Signed-off-by: Aaron Conole <aconole@redhat.com> Tested-by: Lukasz Wojciechowski <l.wojciechow@partner.samsung.com> Reviewed-by: Lukasz Wojciechowski <l.wojciechow@partner.samsung.com>
2020-04-20 19:25:23 +00:00
F: app/test/test_ipfrag.c
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: examples/ip_fragmentation/
F: doc/guides/sample_app_ug/ip_frag.rst
F: examples/ip_reassembly/
F: doc/guides/sample_app_ug/ip_reassembly.rst
lib/gro: add Generic Receive Offload API framework Generic Receive Offload (GRO) is a widely used SW-based offloading technique to reduce per-packet processing overhead. It gains performance by reassembling small packets into large ones. This patchset is to support GRO in DPDK. To support GRO, this patch implements a GRO API framework. To enable more flexibility to applications, DPDK GRO is implemented as a user library. Applications explicitly use the GRO library to merge small packets into large ones. DPDK GRO provides two reassembly modes. One is called lightweight mode, the other is called heavyweight mode. If applications want to merge packets in a simple way and the number of packets is relatively small, they can use the lightweight mode. If applications need more fine-grained controls, they can choose the heavyweight mode. rte_gro_reassemble_burst is the main reassembly API which is used in lightweight mode and processes N packets at a time. For applications, performing GRO in lightweight mode is simple. They just need to invoke rte_gro_reassemble_burst. Applications can get GROed packets as soon as rte_gro_reassemble_burst returns. rte_gro_reassemble is the main reassembly API which is used in heavyweight mode and tries to merge N inputted packets with the packets in GRO reassembly tables. For applications, performing GRO in heavyweight mode is relatively complicated. Before performing GRO, applications need to create a GRO context object, which keeps reassembly tables of desired GRO types, by rte_gro_ctx_create. Then applications can use rte_gro_reassemble to merge packets. The GROed packets are in the reassembly tables of the GRO context object. If applications want to get them, applications need to manually flush them by flush API. Signed-off-by: Jiayu Hu <jiayu.hu@intel.com> Reviewed-by: Jianfeng Tan <jianfeng.tan@intel.com>
2017-07-09 05:46:44 +00:00
Generic Receive Offload - EXPERIMENTAL
M: Jiayu Hu <jiayu.hu@intel.com>
F: lib/librte_gro/
doc: add GRO guide Add prog_guide doc to explain the design of the GRO library. Signed-off-by: Jiayu Hu <jiayu.hu@intel.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2017-08-04 09:59:16 +00:00
F: doc/guides/prog_guide/generic_receive_offload_lib.rst
lib/gro: add Generic Receive Offload API framework Generic Receive Offload (GRO) is a widely used SW-based offloading technique to reduce per-packet processing overhead. It gains performance by reassembling small packets into large ones. This patchset is to support GRO in DPDK. To support GRO, this patch implements a GRO API framework. To enable more flexibility to applications, DPDK GRO is implemented as a user library. Applications explicitly use the GRO library to merge small packets into large ones. DPDK GRO provides two reassembly modes. One is called lightweight mode, the other is called heavyweight mode. If applications want to merge packets in a simple way and the number of packets is relatively small, they can use the lightweight mode. If applications need more fine-grained controls, they can choose the heavyweight mode. rte_gro_reassemble_burst is the main reassembly API which is used in lightweight mode and processes N packets at a time. For applications, performing GRO in lightweight mode is simple. They just need to invoke rte_gro_reassemble_burst. Applications can get GROed packets as soon as rte_gro_reassemble_burst returns. rte_gro_reassemble is the main reassembly API which is used in heavyweight mode and tries to merge N inputted packets with the packets in GRO reassembly tables. For applications, performing GRO in heavyweight mode is relatively complicated. Before performing GRO, applications need to create a GRO context object, which keeps reassembly tables of desired GRO types, by rte_gro_ctx_create. Then applications can use rte_gro_reassemble to merge packets. The GROed packets are in the reassembly tables of the GRO context object. If applications want to get them, applications need to manually flush them by flush API. Signed-off-by: Jiayu Hu <jiayu.hu@intel.com> Reviewed-by: Jianfeng Tan <jianfeng.tan@intel.com>
2017-07-09 05:46:44 +00:00
doc: add GSO programmer's guide Add programmer's guide doc to explain the design and use of the GSO library. Signed-off-by: Mark Kavanagh <mark.b.kavanagh@intel.com> Signed-off-by: Jiayu Hu <jiayu.hu@intel.com> Acked-by: John McNamara <john.mcnamara@intel.com> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
2017-10-07 14:56:44 +00:00
Generic Segmentation Offload
M: Jiayu Hu <jiayu.hu@intel.com>
F: lib/librte_gso/
F: doc/guides/prog_guide/generic_segmentation_offload_lib.rst
lib: introduce IPsec library Introduce librte_ipsec library. The library is supposed to utilize existing DPDK crypto-dev and security API to provide application with transparent IPsec processing API. That initial commit provides some base API to manage IPsec Security Association (SA) object. Signed-off-by: Mohammad Abdul Awal <mohammad.abdul.awal@intel.com> Signed-off-by: Konstantin Ananyev <konstantin.ananyev@intel.com> Acked-by: Declan Doherty <declan.doherty@intel.com> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
2019-01-10 21:06:28 +00:00
IPsec - EXPERIMENTAL
M: Konstantin Ananyev <konstantin.ananyev@intel.com>
T: git://dpdk.org/next/dpdk-next-crypto
F: lib/librte_ipsec/
M: Bernard Iremonger <bernard.iremonger@intel.com>
test/ipsec: add performance cases Add new test-case to measure performance of IPsec data-path functions. Signed-off-by: Savinay Dharmappa <savinay.dharmappa@intel.com> Tested-by: Konstantin Ananyev <konstantin.ananyev@intel.com> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
2020-04-23 15:25:04 +00:00
F: app/test/test_ipsec*
doc: add IPsec library guide Add IPsec library guide and update release notes. Signed-off-by: Bernard Iremonger <bernard.iremonger@intel.com> Signed-off-by: Konstantin Ananyev <konstantin.ananyev@intel.com> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
2019-01-10 21:06:34 +00:00
F: doc/guides/prog_guide/ipsec_lib.rst
test/ipsec: add SAD autotests add unittests for ipsec SAD library Signed-off-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com> Acked-by: Akhil Goyal <akhil.goyal@nxp.com> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com> Tested-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
2019-10-21 14:35:45 +00:00
M: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
app/test-sad: add test application for IPsec SAD Introduce new application to provide user to evaluate and perform custom functional and performance tests for IPsec SAD implementation. According to our measurements on SKX for 1M entries average lookup cost is ~80 cycles, average add cost ~500 cycles. Signed-off-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com> Acked-by: Akhil Goyal <akhil.goyal@nxp.com> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com> Tested-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
2019-10-21 14:35:46 +00:00
F: app/test-sad/
lib: introduce IPsec library Introduce librte_ipsec library. The library is supposed to utilize existing DPDK crypto-dev and security API to provide application with transparent IPsec processing API. That initial commit provides some base API to manage IPsec Security Association (SA) object. Signed-off-by: Mohammad Abdul Awal <mohammad.abdul.awal@intel.com> Signed-off-by: Konstantin Ananyev <konstantin.ananyev@intel.com> Acked-by: Declan Doherty <declan.doherty@intel.com> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
2019-01-10 21:06:28 +00:00
flow_classify: introduce flow classify library The following APIs's are implemented in the librte_flow_classify library: rte_flow_classifier_create rte_flow_classifier_free rte_flow_classifier_query rte_flow_classify_table_create rte_flow_classify_table_entry_add rte_flow_classify_table_entry_delete The following librte_table API's are used: f_create to create a table. f_add to add a rule to the table. f_del to delete a rule from the table. f_free to free a table f_lookup to match packets with the rules. The library supports counting of IPv4 five tupple packets only, ie IPv4 UDP, TCP and SCTP packets. Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Signed-off-by: Bernard Iremonger <bernard.iremonger@intel.com> Acked-by: Jasvinder Singh <jasvinder.singh@intel.com>
2017-10-24 17:28:00 +00:00
Flow Classify - EXPERIMENTAL
M: Bernard Iremonger <bernard.iremonger@intel.com>
F: lib/librte_flow_classify/
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_flow_classify*
doc: add flow classify guides The Flow Classify Library Programmers Guide documents librte_flow_classify. The Flow Classify Sample Application Guide documents the flow_classify sample application which is used to demonstrate the use of the Flow Classify Library, librte_flow_classify. Signed-off-by: Bernard Iremonger <bernard.iremonger@intel.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2017-11-03 11:13:55 +00:00
F: doc/guides/prog_guide/flow_classify_lib.rst
flow_classify: introduce flow classify library The following APIs's are implemented in the librte_flow_classify library: rte_flow_classifier_create rte_flow_classifier_free rte_flow_classifier_query rte_flow_classify_table_create rte_flow_classify_table_entry_add rte_flow_classify_table_entry_delete The following librte_table API's are used: f_create to create a table. f_add to add a rule to the table. f_del to delete a rule from the table. f_free to free a table f_lookup to match packets with the rules. The library supports counting of IPv4 five tupple packets only, ie IPv4 UDP, TCP and SCTP packets. Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Signed-off-by: Bernard Iremonger <bernard.iremonger@intel.com> Acked-by: Jasvinder Singh <jasvinder.singh@intel.com>
2017-10-24 17:28:00 +00:00
F: examples/flow_classify/
doc: add flow classify guides The Flow Classify Library Programmers Guide documents librte_flow_classify. The Flow Classify Sample Application Guide documents the flow_classify sample application which is used to demonstrate the use of the Flow Classify Library, librte_flow_classify. Signed-off-by: Bernard Iremonger <bernard.iremonger@intel.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2017-11-03 11:13:55 +00:00
F: doc/guides/sample_app_ug/flow_classify.rst
flow_classify: introduce flow classify library The following APIs's are implemented in the librte_flow_classify library: rte_flow_classifier_create rte_flow_classifier_free rte_flow_classifier_query rte_flow_classify_table_create rte_flow_classify_table_entry_add rte_flow_classify_table_entry_delete The following librte_table API's are used: f_create to create a table. f_add to add a rule to the table. f_del to delete a rule from the table. f_free to free a table f_lookup to match packets with the rules. The library supports counting of IPv4 five tupple packets only, ie IPv4 UDP, TCP and SCTP packets. Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com> Signed-off-by: Bernard Iremonger <bernard.iremonger@intel.com> Acked-by: Jasvinder Singh <jasvinder.singh@intel.com>
2017-10-24 17:28:00 +00:00
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
Distributor
maintainers: add to distributor lib maintainers Signed-off-by: David Hunt <david.hunt@intel.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2017-03-20 10:08:42 +00:00
M: David Hunt <david.hunt@intel.com>
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: lib/librte_distributor/
F: doc/guides/prog_guide/packet_distrib_lib.rst
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_distributor*
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: examples/distributor/
F: doc/guides/sample_app_ug/dist_app.rst
maintainers: add and claim reorder Add files related to reorder library and claim it. Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-02-18 14:58:18 +00:00
Reorder
maintainers: replace for reorder library Updated maintainers list for reorder library Signed-off-by: Reshma Pattan <reshma.pattan@intel.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2015-10-21 10:50:43 +00:00
M: Reshma Pattan <reshma.pattan@intel.com>
maintainers: add and claim reorder Add files related to reorder library and claim it. Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-02-18 14:58:18 +00:00
F: lib/librte_reorder/
F: doc/guides/prog_guide/reorder_lib.rst
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_reorder*
maintainers: add and claim reorder Add files related to reorder library and claim it. Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-02-18 14:58:18 +00:00
F: examples/packet_ordering/
F: doc/guides/sample_app_ug/packet_ordering.rst
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
Hierarchical scheduler
maintainers: claim metering, sched and packet framework As original author of these DPDK components, I am volunteering to maintain them going forward: - Traffic Metering - Hierarchical Scheduler - Packet Framework - Configuration File Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com> Acked-by: Helin Zhang <helin.zhang@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-02-04 15:53:25 +00:00
M: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
maintainers: add co-maintainer to sched library Add myself as a co-maintainer to dpdk sched library. Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
2019-07-26 16:42:15 +00:00
M: Jasvinder Singh <jasvinder.singh@intel.com>
maintainers: set git tree for packet framework and QoS Mark librte_meter and librte_sched as being handled in the dpdk-next-qos subtree. The packet framework bits go through dpdk-next-pipeline. Signed-off-by: David Marchand <david.marchand@redhat.com>
2020-01-14 13:09:02 +00:00
T: git://dpdk.org/next/dpdk-next-qos
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: lib/librte_sched/
F: doc/guides/prog_guide/qos_framework.rst
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_red.c
F: app/test/test_sched.c
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: examples/qos_sched/
F: doc/guides/sample_app_ug/qos_scheduler.rst
pdump: add new library for packet capture The librte_pdump library provides a framework for packet capturing in dpdk. The library provides set of APIs to initialize the packet capture framework, to enable or disable the packet capture, and to uninitialize it. The librte_pdump library works on a client/server model. The server is responsible for enabling or disabling the packet capture and the clients are responsible for requesting the enabling or disabling of the packet capture. Enabling APIs are supported with port, queue, ring and mempool parameters. Applications should pass on this information to get the packets from the dpdk ports. For enabling requests from applications, library creates the client request containing the mempool, ring, port and queue information and sends the request to the server. After receiving the request, server registers the Rx and Tx callbacks for all the port and queues. After the callbacks registration, registered callbacks will get the Rx and Tx packets. Packets then will be copied to the new mbufs that are allocated from the user passed mempool. These new mbufs then will be enqueued to the application passed ring. Applications need to dequeue the mbufs from the rings and direct them to the devices like pcap vdev for viewing the packets outside of the dpdk using the packet capture tools. For disabling requests, library creates the client request containing the port and queue information and sends the request to the server. After receiving the request, server removes the Rx and Tx callback for all the port and queues. Signed-off-by: Reshma Pattan <reshma.pattan@intel.com> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
2016-06-15 14:06:22 +00:00
Packet capture
M: Reshma Pattan <reshma.pattan@intel.com>
F: lib/librte_pdump/
F: doc/guides/prog_guide/pdump_lib.rst
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_pdump.*
app/pdump: add tool for packet capturing The new pdump tool is added for packet capturing on dpdk. This tool runs as secondary process by default. Tool facilitates the command line options like port, device_id, queue which user should pass on to the tool to request the packet capture on those devices. Tool creates the rte ring, mempool and pcap vdev and calls the enable API of the pdump library with port/device_id, queue, ring and mempool as arguments to enable the packet capture on specific devices and gets the packets from the primary process over the ring. Once the packets are received, those packets will be send to the pcap vdev. Tool can be terminated by using ctrl+c(SIGINT) upon which tool calls the disable API of the pdump library to disable the packet capture and dequeues the rest of the packets from the ring and sends them on to the pcap vdev, then after releases all allocated resources. Signed-off-by: Reshma Pattan <reshma.pattan@intel.com> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
2016-06-15 14:06:23 +00:00
F: app/pdump/
doc: move tool guides in their own subdirectory This is to clarify the scope of these documents that are more tools than sample applications. Also this is a preparation step to add more tools and generate man pages off of their rst files. Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com> Acked-by: Luca Boccassi <lboccass@brocade.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-08-31 07:50:09 +00:00
F: doc/guides/tools/pdump.rst
pdump: add new library for packet capture The librte_pdump library provides a framework for packet capturing in dpdk. The library provides set of APIs to initialize the packet capture framework, to enable or disable the packet capture, and to uninitialize it. The librte_pdump library works on a client/server model. The server is responsible for enabling or disabling the packet capture and the clients are responsible for requesting the enabling or disabling of the packet capture. Enabling APIs are supported with port, queue, ring and mempool parameters. Applications should pass on this information to get the packets from the dpdk ports. For enabling requests from applications, library creates the client request containing the mempool, ring, port and queue information and sends the request to the server. After receiving the request, server registers the Rx and Tx callbacks for all the port and queues. After the callbacks registration, registered callbacks will get the Rx and Tx packets. Packets then will be copied to the new mbufs that are allocated from the user passed mempool. These new mbufs then will be enqueued to the application passed ring. Applications need to dequeue the mbufs from the rings and direct them to the devices like pcap vdev for viewing the packets outside of the dpdk using the packet capture tools. For disabling requests, library creates the client request containing the port and queue information and sends the request to the server. After receiving the request, server removes the Rx and Tx callback for all the port and queues. Signed-off-by: Reshma Pattan <reshma.pattan@intel.com> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
2016-06-15 14:06:22 +00:00
test/pdump: add unit test for pdump library Unit test cases are added for pdump library. Primary process will act as server, forks a child secondary process. Secondary process acts as client. Server will do pdump init to serve any pdump client requests. Server will create a vdev, send/receive packets continuously in a separate thread. Client will create virtual rings to receive the packet dump. Client sends pdump enable/disable requests using either port/device id. Packet flow direction can be tx/rx/tx&rx. In Server, appropriate pdump callbacks are triggered, when packets are transmitted/received. Pdump packet is copied to client rings. Signed-off-by: Naga Suresh Somarowthu <naga.sureshx.somarowthu@intel.com> Reviewed-by: Reshma Pattan <reshma.pattan@intel.com>
2018-10-08 12:12:47 +00:00
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
Packet Framework
----------------
maintainers: claim metering, sched and packet framework As original author of these DPDK components, I am volunteering to maintain them going forward: - Traffic Metering - Hierarchical Scheduler - Packet Framework - Configuration File Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com> Acked-by: Helin Zhang <helin.zhang@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-02-04 15:53:25 +00:00
M: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
maintainers: set git tree for packet framework and QoS Mark librte_meter and librte_sched as being handled in the dpdk-next-qos subtree. The packet framework bits go through dpdk-next-pipeline. Signed-off-by: David Marchand <david.marchand@redhat.com>
2020-01-14 13:09:02 +00:00
T: git://dpdk.org/next/dpdk-next-pipeline
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: lib/librte_pipeline/
F: lib/librte_port/
F: lib/librte_table/
F: doc/guides/prog_guide/packet_framework.rst
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_table*
app/pipeline: move from test directory Move to the app directory, and add to meson build. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:01 +00:00
F: app/test-pipeline/
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: doc/guides/sample_app_ug/test_pipeline.rst
F: examples/ip_pipeline/
doc: update ip pipeline app guide Added more extensive documentation for ip_pipeline application. Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com> Acked-by: Jasvinder Singh <jasvinder.singh@intel.com> Acked-by: Piotr Azarewicz <piotrx.t.azarewicz@intel.com> Acked-by: John McNamara <john.mcnamara@intel.com> [Thomas: keep in doc/guides/sample_app_ug/ directory]
2015-08-11 16:47:08 +00:00
F: doc/guides/sample_app_ug/ip_pipeline.rst
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
Algorithms
----------
ACL
maintainers: claim IP fragmentation and ACL Signed-off-by: Konstantin Ananyev <konstantin.ananyev@intel.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-02-06 12:35:49 +00:00
M: Konstantin Ananyev <konstantin.ananyev@intel.com>
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: lib/librte_acl/
F: doc/guides/prog_guide/packet_classif_access_ctrl.rst
app/acl: move from test directory Move to "app" directory and enable with meson build. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
2019-02-26 12:19:00 +00:00
F: app/test-acl/
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_acl.*
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: examples/l3fwd-acl/
F: doc/guides/sample_app_ug/l3_forward_access_ctrl.rst
efd: new Elastic Flow Distributor library Elastic Flow Distributor (EFD) is a distributor library that uses perfect hashing to determine a target/value for a given incoming flow key. It has the following advantages: - First, because it uses perfect hashing, it does not store the key itself and hence lookup performance is not dependent on the key size. - Second, the target/value can be any arbitrary value hence the system designer and/or operator can better optimize service rates and inter-cluster network traffic locating. - Third, since the storage requirement is much smaller than a hash-based flow table (i.e. better fit for CPU cache), EFD can scale to millions of flow keys. Finally, with current optimized library implementation performance is fully scalable with number of CPU cores. Signed-off-by: Byron Marohn <byron.marohn@intel.com> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Signed-off-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com> Acked-by: Christian Maciocco <christian.maciocco@intel.com>
2017-01-17 22:23:51 +00:00
EFD
M: Byron Marohn <byron.marohn@intel.com>
maintainers: update for EFD library Add myself as co-maintainer to EFD library to replace Pablo. Signed-off-by: Yipeng Wang <yipeng1.wang@intel.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2019-09-11 18:06:37 +00:00
M: Yipeng Wang <yipeng1.wang@intel.com>
efd: new Elastic Flow Distributor library Elastic Flow Distributor (EFD) is a distributor library that uses perfect hashing to determine a target/value for a given incoming flow key. It has the following advantages: - First, because it uses perfect hashing, it does not store the key itself and hence lookup performance is not dependent on the key size. - Second, the target/value can be any arbitrary value hence the system designer and/or operator can better optimize service rates and inter-cluster network traffic locating. - Third, since the storage requirement is much smaller than a hash-based flow table (i.e. better fit for CPU cache), EFD can scale to millions of flow keys. Finally, with current optimized library implementation performance is fully scalable with number of CPU cores. Signed-off-by: Byron Marohn <byron.marohn@intel.com> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Signed-off-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com> Acked-by: Christian Maciocco <christian.maciocco@intel.com>
2017-01-17 22:23:51 +00:00
F: lib/librte_efd/
doc: add EFD library section in programmers guide Signed-off-by: Sameh Gobriel <sameh.gobriel@intel.com> Acked-by: Christian Maciocco <christian.maciocco@intel.com>
2017-01-17 22:23:55 +00:00
F: doc/guides/prog_guide/efd_lib.rst
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_efd*
examples/server_node_efd: renamed from flow_distributor To avoid confusion with distributor app, this commit renames the flow-distributor sample app to server_node_efd, since it shows how to use the EFD library and it is based on a server/nodes model. Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-01-24 09:06:14 +00:00
F: examples/server_node_efd/
F: doc/guides/sample_app_ug/server_node_efd.rst
efd: new Elastic Flow Distributor library Elastic Flow Distributor (EFD) is a distributor library that uses perfect hashing to determine a target/value for a given incoming flow key. It has the following advantages: - First, because it uses perfect hashing, it does not store the key itself and hence lookup performance is not dependent on the key size. - Second, the target/value can be any arbitrary value hence the system designer and/or operator can better optimize service rates and inter-cluster network traffic locating. - Third, since the storage requirement is much smaller than a hash-based flow table (i.e. better fit for CPU cache), EFD can scale to millions of flow keys. Finally, with current optimized library implementation performance is fully scalable with number of CPU cores. Signed-off-by: Byron Marohn <byron.marohn@intel.com> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Signed-off-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com> Acked-by: Christian Maciocco <christian.maciocco@intel.com>
2017-01-17 22:23:51 +00:00
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
Hashes
maintainers: claim maintainership of hash library Add Yipeng and Sameh as additional maintainers. Signed-off-by: Yipeng Wang <yipeng1.wang@intel.com> Signed-off-by: Sameh Gobriel <sameh.gobriel@intel.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2019-01-08 15:08:34 +00:00
M: Yipeng Wang <yipeng1.wang@intel.com>
M: Sameh Gobriel <sameh.gobriel@intel.com>
maintainers: claim hash and lpm libraries Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Acked-by: Helin Zhang <helin.zhang@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-02-06 13:57:07 +00:00
M: Bruce Richardson <bruce.richardson@intel.com>
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: lib/librte_hash/
F: doc/guides/prog_guide/hash_lib.rst
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_*hash*
F: app/test/test_func_reentrancy.c
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
LPM
maintainers: claim hash and lpm libraries Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Acked-by: Helin Zhang <helin.zhang@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-02-06 13:57:07 +00:00
M: Bruce Richardson <bruce.richardson@intel.com>
maintainers: claim co-maintainership of LPM library Signed-off-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
2019-02-05 13:57:33 +00:00
M: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: lib/librte_lpm/
F: doc/guides/prog_guide/lpm*
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_lpm*
F: app/test/test_func_reentrancy.c
F: app/test/test_xmmt_ops.h
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
member: implement main API Membership library is an extension and generalization of a traditional filter (for example Bloom Filter and cuckoo filter) structure. In general, the Membership library is a data structure that provides a "set-summary" and responds to set-membership queries of whether a certain element belongs to a set(s). A membership test for an element will return the set this element belongs to or not-found if the element is never inserted into the set-summary. The results of the membership test are not 100% accurate. Certain false positive or false negative probability could exist. However, comparing to a "full-blown" complete list of elements, a "set-summary" is memory efficient and fast on lookup. This patch adds the main API definition. Signed-off-by: Yipeng Wang <yipeng1.wang@intel.com> Reviewed-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-10-04 03:12:19 +00:00
Membership - EXPERIMENTAL
M: Yipeng Wang <yipeng1.wang@intel.com>
M: Sameh Gobriel <sameh.gobriel@intel.com>
F: lib/librte_member/
doc: add membership documentation This patch adds the documentation for membership library. Signed-off-by: Yipeng Wang <yipeng1.wang@intel.com> Reviewed-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2017-10-04 03:12:25 +00:00
F: doc/guides/prog_guide/member_lib.rst
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_member*
member: implement main API Membership library is an extension and generalization of a traditional filter (for example Bloom Filter and cuckoo filter) structure. In general, the Membership library is a data structure that provides a "set-summary" and responds to set-membership queries of whether a certain element belongs to a set(s). A membership test for an element will return the set this element belongs to or not-found if the element is never inserted into the set-summary. The results of the membership test are not 100% accurate. Certain false positive or false negative probability could exist. However, comparing to a "full-blown" complete list of elements, a "set-summary" is memory efficient and fast on lookup. This patch adds the main API definition. Signed-off-by: Yipeng Wang <yipeng1.wang@intel.com> Reviewed-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2017-10-04 03:12:19 +00:00
fib: add FIB library Add FIB (Forwarding Information Base) library. This library implements a dataplane structures and algorithms designed for fast longest prefix match. Internally it consists of two parts - RIB (control plane ops) and implementation for the dataplane tasks. Initial version provides two implementations for both IPv4 and IPv6: dummy (uses RIB as a dataplane) and DIR24_8 (same as current LPM) Due to proposed design it allows to extend FIB with new algorithms in future (for example DXR, poptrie, etc). Signed-off-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
2019-11-01 15:21:38 +00:00
RIB/FIB - EXPERIMENTAL
rib: add RIB library Add RIB (Routing Information Base) library. This library implements an IPv4 routing table optimized for control plane operations. It implements a control plane struct containing routes in a tree and provides fast add/del operations for routes. Also it allows to perform fast subtree traversals (i.e. retrieve existing subroutes for a given prefix). This structure will be used as a control plane helper structure for FIB implementation. Also it might be used standalone in other different places such as bitmaps for example. Internal implementation is level compressed binary trie. Signed-off-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
2019-11-01 15:21:34 +00:00
M: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
F: lib/librte_rib/
test/rib: add autotests Functional tests for the new RIB library. Signed-off-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
2019-11-01 15:21:35 +00:00
F: app/test/test_rib*
fib: add FIB library Add FIB (Forwarding Information Base) library. This library implements a dataplane structures and algorithms designed for fast longest prefix match. Internally it consists of two parts - RIB (control plane ops) and implementation for the dataplane tasks. Initial version provides two implementations for both IPv4 and IPv6: dummy (uses RIB as a dataplane) and DIR24_8 (same as current LPM) Due to proposed design it allows to extend FIB with new algorithms in future (for example DXR, poptrie, etc). Signed-off-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
2019-11-01 15:21:38 +00:00
F: lib/librte_fib/
test/fib: add autotests Functional tests for the new FIB library. Signed-off-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
2019-11-01 15:21:42 +00:00
F: app/test/test_fib*
app/test-fib: add test application for FIB Introduce new application to provide user to evaluate and perform custom functional and performance tests for FIB library. Signed-off-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
2019-12-11 18:45:04 +00:00
F: app/test-fib/
rib: add RIB library Add RIB (Routing Information Base) library. This library implements an IPv4 routing table optimized for control plane operations. It implements a control plane struct containing routes in a tree and provides fast add/del operations for routes. Also it allows to perform fast subtree traversals (i.e. retrieve existing subroutes for a given prefix). This structure will be used as a control plane helper structure for FIB implementation. Also it might be used standalone in other different places such as bitmaps for example. Internal implementation is level compressed binary trie. Signed-off-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
2019-11-01 15:21:34 +00:00
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
Traffic metering
maintainers: claim metering, sched and packet framework As original author of these DPDK components, I am volunteering to maintain them going forward: - Traffic Metering - Hierarchical Scheduler - Packet Framework - Configuration File Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com> Acked-by: Helin Zhang <helin.zhang@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-02-04 15:53:25 +00:00
M: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
maintainers: set git tree for packet framework and QoS Mark librte_meter and librte_sched as being handled in the dpdk-next-qos subtree. The packet framework bits go through dpdk-next-pipeline. Signed-off-by: David Marchand <david.marchand@redhat.com>
2020-01-14 13:09:02 +00:00
T: git://dpdk.org/next/dpdk-next-qos
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: lib/librte_meter/
F: doc/guides/sample_app_ug/qos_scheduler.rst
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_meter.c
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: examples/qos_meter/
F: doc/guides/sample_app_ug/qos_metering.rst
maintainers: fix typo and ordering Fix logical/alphabetical ordering, spacing, and syntax typo. Fixes: 8fb3b2576025 ("maintainers: call out subtree committers") Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2018-04-23 01:18:35 +00:00
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
Other libraries
---------------
Configuration file
maintainers: claim metering, sched and packet framework As original author of these DPDK components, I am volunteering to maintain them going forward: - Traffic Metering - Hierarchical Scheduler - Packet Framework - Configuration File Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com> Acked-by: Helin Zhang <helin.zhang@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-02-04 15:53:25 +00:00
M: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: lib/librte_cfgfile/
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_cfgfile.c
F: app/test/test_cfgfiles/
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
Interactive command line
maintainers: claim mbuf, mempool, ring, mk, kvargs, cmdline I'm volunteer to maintain the following components of dpdk: - mbuf packet api - mempool library - ring library - build system - kvargs - command line library Note: I've split rte_mempool and rte_malloc as these two libraries are different enough. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-01-30 15:52:22 +00:00
M: Olivier Matz <olivier.matz@6wind.com>
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: lib/librte_cmdline/
app/cmdline: move from test directory Move app to "app" directory and enable with meson build. For consistency of naming, the subdirectory is also renamed from cmdline_test to test-cmdline. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:18:59 +00:00
F: app/test-cmdline/
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_cmdline*
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: examples/cmdline/
F: doc/guides/sample_app_ug/cmd_line.rst
Key/Value parsing
maintainers: claim mbuf, mempool, ring, mk, kvargs, cmdline I'm volunteer to maintain the following components of dpdk: - mbuf packet api - mempool library - ring library - build system - kvargs - command line library Note: I've split rte_mempool and rte_malloc as these two libraries are different enough. Signed-off-by: Olivier Matz <olivier.matz@6wind.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-01-30 15:52:22 +00:00
M: Olivier Matz <olivier.matz@6wind.com>
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: lib/librte_kvargs/
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_kvargs.c
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
rcu: add RCU library supporting QSBR mechanism Add RCU library supporting quiescent state based memory reclamation method. This library helps identify the quiescent state of the reader threads so that the writers can free the memory associated with the lock less data structures. Signed-off-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com> Reviewed-by: Steve Capper <steve.capper@arm.com> Reviewed-by: Gavin Hu <gavin.hu@arm.com> Reviewed-by: Ola Liljedahl <ola.liljedahl@arm.com> Acked-by: Paul E. McKenney <paulmck@linux.ibm.com> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com> Tested-by: Jerin Jacob <jerinj@marvell.com> Tested-by: Ruifeng Wang <ruifeng.wang@arm.com> Tested-by: Hemant Agrawal <hemant.agrawal@nxp.com>
2019-05-01 03:54:16 +00:00
RCU - EXPERIMENTAL
M: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
F: lib/librte_rcu/
maintainers: fix added or removed files Reference to test/Makefile was forgotten when removing this file. Reference to app/test/test_rcu* was forgotten when adding the files. Fixes: a9de470cc7c0 ("test: move to app directory") Fixes: b87089b0bb19 ("test/rcu: add API and functional tests") Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
2019-05-02 14:53:45 +00:00
F: app/test/test_rcu*
rcu: add RCU library supporting QSBR mechanism Add RCU library supporting quiescent state based memory reclamation method. This library helps identify the quiescent state of the reader threads so that the writers can free the memory associated with the lock less data structures. Signed-off-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com> Reviewed-by: Steve Capper <steve.capper@arm.com> Reviewed-by: Gavin Hu <gavin.hu@arm.com> Reviewed-by: Ola Liljedahl <ola.liljedahl@arm.com> Acked-by: Paul E. McKenney <paulmck@linux.ibm.com> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com> Tested-by: Jerin Jacob <jerinj@marvell.com> Tested-by: Ruifeng Wang <ruifeng.wang@arm.com> Tested-by: Hemant Agrawal <hemant.agrawal@nxp.com>
2019-05-01 03:54:16 +00:00
F: doc/guides/prog_guide/rcu_lib.rst
pci: introduce library and driver The PCI lib defines the types and methods allowing to use PCI elements. The PCI bus implements a bus driver for PCI devices by constructing rte_bus elements using the PCI lib. Move the relevant code out of the EAL to its expected place. Libraries, drivers, unit tests and applications are updated to use the new rte_bus_pci.h header when necessary. Signed-off-by: Gaetan Rivet <gaetan.rivet@6wind.com>
2017-10-26 10:06:08 +00:00
PCI
maintainers: update for failsafe and PCI library My email address has changed, gaetan.rivet@6wind.com is no longer valid. Cc: stable@dpdk.org Signed-off-by: Gaetan Rivet <grive@u256.net>
2020-01-08 14:13:32 +00:00
M: Gaetan Rivet <grive@u256.net>
pci: introduce library and driver The PCI lib defines the types and methods allowing to use PCI elements. The PCI bus implements a bus driver for PCI devices by constructing rte_bus elements using the PCI lib. Move the relevant code out of the EAL to its expected place. Libraries, drivers, unit tests and applications are updated to use the new rte_bus_pci.h header when necessary. Signed-off-by: Gaetan Rivet <gaetan.rivet@6wind.com>
2017-10-26 10:06:08 +00:00
F: lib/librte_pci/
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
Power management
maintainers: volunteer to take power management Signed-off-by: David Hunt <david.hunt@intel.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2017-08-04 14:07:34 +00:00
M: David Hunt <david.hunt@intel.com>
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: lib/librte_power/
F: doc/guides/prog_guide/power_man.rst
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_power*
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: examples/l3fwd-power/
F: doc/guides/sample_app_ug/l3_forward_power_man.rst
F: examples/vm_power_manager/
F: doc/guides/sample_app_ug/vm_power_management.rst
Timers
maintainers: claim responsibility for timers Signed-off-by: Robert Sanford <rsanford@akamai.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-02-25 20:18:05 +00:00
M: Robert Sanford <rsanford@akamai.com>
maintainers: claim responsibility for timer library Add myself as co-maintainer for the timer library. Signed-off-by: Erik Gabriel Carrillo <erik.g.carrillo@intel.com> Acked-by: Robert Sanford <rsanford@akamai.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2019-03-11 16:13:09 +00:00
M: Erik Gabriel Carrillo <erik.g.carrillo@intel.com>
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: lib/librte_timer/
F: doc/guides/prog_guide/timer_lib.rst
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_timer*
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: examples/timer/
F: doc/guides/sample_app_ug/timer.rst
maintainers: claim responsibility for jobstats library and example Signed-off-by: Pawel Wodkowski <pawelx.wodkowski@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-02-24 16:33:25 +00:00
Job statistics
F: lib/librte_jobstats/
F: examples/l2fwd-jobstats/
doc: add jobstats sample guide Signed-off-by: Pawel Wodkowski <pawelx.wodkowski@intel.com> [Thomas: fix image extensions for PDF]
2015-03-18 10:20:39 +00:00
F: doc/guides/sample_app_ug/l2_forward_job_stats.rst
maintainers: claim responsibility for jobstats library and example Signed-off-by: Pawel Wodkowski <pawelx.wodkowski@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-02-24 16:33:25 +00:00
metrics: add information metrics library This patch adds a new information metrics library. This Metrics library implements a mechanism by which producers can publish numeric information for later querying by consumers. Metrics themselves are statistics that are not generated by PMDs, and hence are not reported via ethdev extended statistics. Metric information is populated using a push model, where producers update the values contained within the metric library by calling an update function on the relevant metrics. Consumers receive metric information by querying the central metric data, which is held in shared memory. Signed-off-by: Remy Horton <remy.horton@intel.com>
2017-03-30 21:00:57 +00:00
Metrics
F: lib/librte_metrics/
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_metrics.c
metrics: add information metrics library This patch adds a new information metrics library. This Metrics library implements a mechanism by which producers can publish numeric information for later querying by consumers. Metrics themselves are statistics that are not generated by PMDs, and hence are not reported via ethdev extended statistics. Metric information is populated using a push model, where producers update the values contained within the metric library by calling an update function on the relevant metrics. Consumers receive metric information by querying the central metric data, which is held in shared memory. Signed-off-by: Remy Horton <remy.horton@intel.com>
2017-03-30 21:00:57 +00:00
bitrate: add bitrate statistics library This patch adds a library that calculates peak and average data-rate statistics. For ethernet devices. These statistics are reported using the metrics library. Signed-off-by: Remy Horton <remy.horton@intel.com>
2017-03-30 21:00:59 +00:00
Bit-rate statistics
F: lib/librte_bitratestats/
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_bitratestats.c
bitrate: add bitrate statistics library This patch adds a library that calculates peak and average data-rate statistics. For ethernet devices. These statistics are reported using the metrics library. Signed-off-by: Remy Horton <remy.horton@intel.com>
2017-03-30 21:00:59 +00:00
latency: added new library for latency stats Add a library designed to calculate latency statistics and report them to the application when queried. The library measures minimum, average and maximum latencies, and jitter in nano seconds. The current implementation supports global latency stats, i.e. per application stats. Signed-off-by: Reshma Pattan <reshma.pattan@intel.com> Signed-off-by: Remy Horton <remy.horton@intel.com> Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com>
2017-03-30 21:01:01 +00:00
Latency statistics
M: Reshma Pattan <reshma.pattan@intel.com>
F: lib/librte_latencystats/
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_latencystats.c
latency: added new library for latency stats Add a library designed to calculate latency statistics and report them to the application when queried. The library measures minimum, average and maximum latencies, and jitter in nano seconds. The current implementation supports global latency stats, i.e. per application stats. Signed-off-by: Reshma Pattan <reshma.pattan@intel.com> Signed-off-by: Remy Horton <remy.horton@intel.com> Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com>
2017-03-30 21:01:01 +00:00
telemetry: introduce infrastructure This patch adds the infrastructure and initial code for the telemetry library. The telemetry init is registered with eal_init(). We can then check to see if --telemetry was passed as an eal option. If --telemetry was parsed, then we call telemetry init at the end of eal init. Control threads are used to get CPU cycles for telemetry, which are configured in this patch also. Signed-off-by: Ciara Power <ciara.power@intel.com> Signed-off-by: Brian Archbold <brian.archbold@intel.com> Signed-off-by: Kevin Laatz <kevin.laatz@intel.com> Signed-off-by: Radu Nicolau <radu.nicolau@intel.com> Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
2018-10-27 09:17:41 +00:00
Telemetry - EXPERIMENTAL
M: Kevin Laatz <kevin.laatz@intel.com>
F: lib/librte_telemetry/
telemetry: add utility functions for creating JSON The functions added in this patch will make it easier for telemetry to convert data to correct JSON responses to telemetry requests. Tests are also added for these json utility functions. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Reviewed-by: Keith Wiles <keith.wiles@intel.com>
2020-04-30 16:01:24 +00:00
F: app/test/test_telemetry*
usertools: add new telemetry script This patch adds a python script that can be used with the new telemetry socket. It connects as a client to the socket, and allows the user send a command and see the JSON response. The example usage below shows the script connecting to the new telemetry socket, and sending three default telemetry commands entered by the user. The response for each command is shown below the user input. Connecting to /var/run/dpdk/rte/dpdk_telemetry.v2 {"version": "DPDK 20.05.0-rc0", "pid": 32794, "max_output_len": 16384} --> / {"/": ["/", "/help", "/info"]} --> /info {"/info": {"version": "DPDK 20.05.0-rc0", "pid": 32794, \ "max_output_len": 16384}} --> /help,/info {"/help": {"/info": "Returns DPDK Telemetry information. \ Takes no parameters"}} Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Signed-off-by: Ciara Power <ciara.power@intel.com> Reviewed-by: Keith Wiles <keith.wiles@intel.com>
2020-04-30 16:01:28 +00:00
F: usertools/dpdk-telemetry*
doc: add telemetry how-to This patch adds all documentation for telemetry. A description on how to use the Telemetry API with a DPDK application is given in this document. It also adds a release notes update for telemetry. Signed-off-by: Ciara Power <ciara.power@intel.com> Signed-off-by: Brian Archbold <brian.archbold@intel.com> Signed-off-by: Kevin Laatz <kevin.laatz@intel.com> Acked-by: Harry van Haaren <harry.van.haaren@intel.com> Acked-by: Marko Kovacevic <marko.kovacevic@intel.com>
2018-10-27 09:17:48 +00:00
F: doc/guides/howto/telemetry.rst
telemetry: introduce infrastructure This patch adds the infrastructure and initial code for the telemetry library. The telemetry init is registered with eal_init(). We can then check to see if --telemetry was passed as an eal option. If --telemetry was parsed, then we call telemetry init at the end of eal init. Control threads are used to get CPU cycles for telemetry, which are configured in this patch also. Signed-off-by: Ciara Power <ciara.power@intel.com> Signed-off-by: Brian Archbold <brian.archbold@intel.com> Signed-off-by: Kevin Laatz <kevin.laatz@intel.com> Signed-off-by: Radu Nicolau <radu.nicolau@intel.com> Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
2018-10-27 09:17:41 +00:00
bpf: add missed experimental tags - add EXPERIMENTAL tag for the section in MAINTAINERS. - add EXPERIMENTAL tag to BPF public API files. - add attribute __rte_experimental to BPF public API declarations. Fixes: 94972f35a02e ("bpf: add BPF loading and execution framework") Fixes: 5dba93ae5f2d ("bpf: add ability to load eBPF program from ELF object file") Fixes: a93ff62a8938 ("bpf: introduce basic Rx/Tx filters") Reported-by: Thomas Monjalon <thomas@monjalon.net> Signed-off-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
2018-05-14 13:15:42 +00:00
BPF - EXPERIMENTAL
bpf: add BPF loading and execution framework librte_bpf provides a framework to load and execute eBPF bytecode inside user-space dpdk based applications. It supports basic set of features from eBPF spec (https://www.kernel.org/doc/Documentation/networking/filter.txt). Not currently supported features: - JIT - cBPF - tail-pointer call - eBPF MAP - skb - function calls for 32-bit apps - mbuf pointer as input parameter for 32-bit apps Signed-off-by: Konstantin Ananyev <konstantin.ananyev@intel.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-05-10 10:23:03 +00:00
M: Konstantin Ananyev <konstantin.ananyev@intel.com>
F: lib/librte_bpf/
examples/bpf: move from test directory The bpf folder didn't actual contain a test application, but instead basic examples of BPF code for use with testpmd. Therefore we can move it to the `examples` folder. Being different, it also needs a README with it, explaining what it is and how to use it. References to the code from the testpmd docs are suitably updated. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
2019-02-26 12:19:02 +00:00
F: examples/bpf/
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_bpf.c
doc: add BPF library guide Signed-off-by: Konstantin Ananyev <konstantin.ananyev@intel.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-05-10 10:23:11 +00:00
F: doc/guides/prog_guide/bpf_lib.rst
bpf: add BPF loading and execution framework librte_bpf provides a framework to load and execute eBPF bytecode inside user-space dpdk based applications. It supports basic set of features from eBPF spec (https://www.kernel.org/doc/Documentation/networking/filter.txt). Not currently supported features: - JIT - cBPF - tail-pointer call - eBPF MAP - skb - function calls for 32-bit apps - mbuf pointer as input parameter for 32-bit apps Signed-off-by: Konstantin Ananyev <konstantin.ananyev@intel.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-05-10 10:23:03 +00:00
graph: define API Graph architecture abstracts the data processing functions as "node" and "link" them together to create a complex "graph" to enable reusable/modular data processing functions. These APIs enables graph framework operations such as create, lookup, dump and destroy on graph and node operations such as clone, edge update, and edge shrink, etc. The API also allows creating the stats cluster to monitor per graph and per node stats. This patch defines the public API for graph support. This patch also adds support for the build infrastructure and update the MAINTAINERS file for the graph subsystem. Signed-off-by: Jerin Jacob <jerinj@marvell.com> Signed-off-by: Kiran Kumar K <kirankumark@marvell.com> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com> Signed-off-by: Nithin Dabilpuram <ndabilpuram@marvell.com>
2020-04-11 14:14:00 +00:00
Graph - EXPERIMENTAL
M: Jerin Jacob <jerinj@marvell.com>
M: Kiran Kumar K <kirankumark@marvell.com>
F: lib/librte_graph/
doc: add graph library guide Adding programmer's guide for Graph library and the inbuilt nodes. This patch also updates the release note for the new libraries. Signed-off-by: Jerin Jacob <jerinj@marvell.com> Signed-off-by: Kiran Kumar K <kirankumark@marvell.com> Signed-off-by: Nithin Dabilpuram <ndabilpuram@marvell.com> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
2020-04-11 14:14:27 +00:00
F: doc/guides/prog_guide/graph_lib.rst
test/graph: add functional tests Adding the unit test to test the functionality of node and graph APIs. Testing includes registering a node, cloning a node, creating a graph, perform graph walk, collecting stats and all node and graph debug APIs. example command to test: echo "graph_autotest" | sudo ./build/app/test/dpdk-test -c 0x30 Signed-off-by: Kiran Kumar K <kirankumark@marvell.com> Signed-off-by: Nithin Dabilpuram <ndabilpuram@marvell.com>
2020-04-11 14:14:12 +00:00
F: app/test/test_graph*
examples/l3fwd-graph: add graph-based l3fwd skeleton Add graph based l3fwd application skeleton with cmdline parsing support inline with normal l3fwd. Signed-off-by: Nithin Dabilpuram <ndabilpuram@marvell.com>
2020-04-11 14:14:24 +00:00
M: Nithin Dabilpuram <ndabilpuram@marvell.com>
F: examples/l3fwd-graph/
doc: add l3fwd-graph application user guide Adding the user guide for l3fwd graph application. Signed-off-by: Nithin Dabilpuram <ndabilpuram@marvell.com>
2020-04-11 14:14:28 +00:00
F: doc/guides/sample_app_ug/l3_forward_graph.rst
graph: define API Graph architecture abstracts the data processing functions as "node" and "link" them together to create a complex "graph" to enable reusable/modular data processing functions. These APIs enables graph framework operations such as create, lookup, dump and destroy on graph and node operations such as clone, edge update, and edge shrink, etc. The API also allows creating the stats cluster to monitor per graph and per node stats. This patch defines the public API for graph support. This patch also adds support for the build infrastructure and update the MAINTAINERS file for the graph subsystem. Signed-off-by: Jerin Jacob <jerinj@marvell.com> Signed-off-by: Kiran Kumar K <kirankumark@marvell.com> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com> Signed-off-by: Nithin Dabilpuram <ndabilpuram@marvell.com>
2020-04-11 14:14:00 +00:00
node: add logging and null node Add log infra for node specific logging. Also, add null rte_node that just ignores all the objects directed to it. Signed-off-by: Nithin Dabilpuram <ndabilpuram@marvell.com> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com> Signed-off-by: Kiran Kumar K <kirankumark@marvell.com>
2020-04-11 14:14:14 +00:00
Nodes - EXPERIMENTAL
M: Nithin Dabilpuram <ndabilpuram@marvell.com>
M: Pavan Nikhilesh <pbhagavatula@marvell.com>
F: lib/librte_node/
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
Test Applications
-----------------
Unit tests framework
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/Makefile
F: app/test/autotest*
F: app/test/commands.c
app/test: remove meson dependency on file in /sys Meson versions 0.52 and 0.53 are being overly smart and detecting the path "/sys/devices/system/cpu/present" in the call to cat in app/test/meson.build and then adding it as a dependency to the build configuration. This causes issues on systems where the timestamp of that file always returns the current time, since it means that the build.ninja file is always out of date, and therefore needs to be rebuilt. We can fix this by just using a simple shell script to return the coremask appropriately for BSD and Linux, and removing that code logic from meson - thereby hiding the use of the /sys file. Fixes: c70622ac6f72 ("test: detect number of cores with meson") Cc: stable@dpdk.org Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2020-01-20 12:22:18 +00:00
F: app/test/get-coremask.sh
test: remove meson dependency on /proc file Meson is detecting the path /proc/sys/vm/nr_hugepages in the call to cat in app/test/meson.build and then adding it as a build dependency. This causes build loop if the timestamp of this file keeps changing. It is fixed by hiding hugepage check in a shell script. Fixes: 77784ef0fba8 ("test: allow no-huge mode for fast-tests") Signed-off-by: Thomas Monjalon <thomas@monjalon.net> Tested-by: Lukasz Wojciechowski <l.wojciechow@partner.samsung.com> Reviewed-by: Lukasz Wojciechowski <l.wojciechow@partner.samsung.com> Acked-by: Aaron Conole <aconole@redhat.com> Reviewed-by: Ruifeng Wang <ruifeng.wang@arm.com> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
2020-04-09 16:41:49 +00:00
F: app/test/has-hugepage.sh
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/packet_burst_generator.c
F: app/test/packet_burst_generator.h
F: app/test/process.h
F: app/test/resource.*
F: app/test/test.c
F: app/test/test.h
F: app/test/test_pmd_perf.c
F: app/test/test_resource.c
F: app/test/virtual_pmd.c
F: app/test/virtual_pmd.h
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
test: add helpers using ring PMD Rx/Tx Added ring pmd based packet rx/tx helper functions for verifying Latency, Bitrate and pdump lib UTs. Signed-off-by: Naga Suresh Somarowthu <naga.sureshx.somarowthu@intel.com> Reviewed-by: Reshma Pattan <reshma.pattan@intel.com> Reviewed-by: Anatoly Burakov <anatoly.burakov@intel.com>
2018-10-08 12:12:44 +00:00
Sample packet helper functions for unit test
M: Reshma Pattan <reshma.pattan@intel.com>
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/sample_packet_forward.c
F: app/test/sample_packet_forward.h
test: add helpers using ring PMD Rx/Tx Added ring pmd based packet rx/tx helper functions for verifying Latency, Bitrate and pdump lib UTs. Signed-off-by: Naga Suresh Somarowthu <naga.sureshx.somarowthu@intel.com> Reviewed-by: Reshma Pattan <reshma.pattan@intel.com> Reviewed-by: Anatoly Burakov <anatoly.burakov@intel.com>
2018-10-08 12:12:44 +00:00
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
Driver testing tool
maintainers: update for testpmd Signed-off-by: Jingjing Wu <jingjing.wu@intel.com> Acked-by: Helin Zhang <helin.zhang@intel.com>
2017-12-04 06:18:26 +00:00
M: Wenzhuo Lu <wenzhuo.lu@intel.com>
maintainers: update for testpmd Replace Jingjing Wu with Beilei Xing. Signed-off-by: Beilei Xing <beilei.xing@intel.com> Acked-by: Jingjing Wu <jingjing.wu@intel.com>
2020-04-26 08:21:53 +00:00
M: Beilei Xing <beilei.xing@intel.com>
maintainers: add maintainer for testpmd Signed-off-by: Bernard Iremonger <bernard.iremonger@intel.com> Acked-by: Wenzhuo Lu <wenzhuo.lu@intel.com> Acked-by: Thomas Monjalon <thomas@monjalon.net>
2018-05-10 09:29:04 +00:00
M: Bernard Iremonger <bernard.iremonger@intel.com>
maintainers: set git tree for test applications Changes on the main test applications should be considered against subtrees where most of the API changes and development happen: - testpmd goes through dpdk-next-net as it is mainly about ethdev, - dpdk-test-compress-perf goes through dpdk-next-crypto since the compress API goes through this tree, - dpdk-test-crypto-perf through dpdk-next-crypto, - dpdk-test-eventdev through dpdk-next-eventdev, Signed-off-by: David Marchand <david.marchand@redhat.com> Acked-by: Jerin Jacob <jerinj@marvell.com> Acked-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Andrew Rybchenko <arybchenko@solarflare.com> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
2020-01-14 09:18:15 +00:00
T: git://dpdk.org/next/dpdk-next-net
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: app/test-pmd/
F: doc/guides/testpmd_app_ug/
doc: add details for compress-perf app Added: - initial version of compression performance test description file. - release note in release_18_11.rst Updated index.rst file Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Signed-off-by: Tomasz Jozwiak <tomaszx.jozwiak@intel.com> Acked-by: Fiona Trahe <fiona.trahe@intel.com> Acked-by: Lee Daly <lee.daly@intel.com> Acked-by: Shally Verma <shally.verma@caviumnetworks.com>
2018-12-12 12:08:03 +00:00
Compression performance test application
maintainers: set git tree for test applications Changes on the main test applications should be considered against subtrees where most of the API changes and development happen: - testpmd goes through dpdk-next-net as it is mainly about ethdev, - dpdk-test-compress-perf goes through dpdk-next-crypto since the compress API goes through this tree, - dpdk-test-crypto-perf through dpdk-next-crypto, - dpdk-test-eventdev through dpdk-next-eventdev, Signed-off-by: David Marchand <david.marchand@redhat.com> Acked-by: Jerin Jacob <jerinj@marvell.com> Acked-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Andrew Rybchenko <arybchenko@solarflare.com> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
2020-01-14 09:18:15 +00:00
T: git://dpdk.org/next/dpdk-next-crypto
doc: add details for compress-perf app Added: - initial version of compression performance test description file. - release note in release_18_11.rst Updated index.rst file Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com> Signed-off-by: Tomasz Jozwiak <tomaszx.jozwiak@intel.com> Acked-by: Fiona Trahe <fiona.trahe@intel.com> Acked-by: Lee Daly <lee.daly@intel.com> Acked-by: Shally Verma <shally.verma@caviumnetworks.com>
2018-12-12 12:08:03 +00:00
F: app/test-compress-perf/
F: doc/guides/tools/comp_perf.rst
app/crypto-perf: introduce performance test application This patchset introduce new application which allows measuring performance parameters of PMDs available in crypto tree. The goal of this application is to replace existing performance tests in app/test. Parameters available are: throughput (--ptest throughput) and latency (--ptest latency). User can use multiply cores to run tests on but only one type of crypto PMD can be measured during single application execution. Cipher parameters, type of device, type of operation and chain mode have to be specified in the command line as application parameters. These parameters are checked using device capabilities structure. Couple of new library functions in librte_cryptodev are introduced for application use. To build the application a CONFIG_RTE_APP_CRYPTO_PERF flag has to be set (it is set by default). Example of usage: -c 0xc0 --vdev crypto_aesni_mb_pmd -w 0000:00:00.0 -- --ptest throughput --devtype crypto_aesni_mb --optype cipher-then-auth --cipher-algo aes-cbc --cipher-op encrypt --cipher-key-sz 16 --auth-algo sha1-hmac --auth-op generate --auth-key-sz 64 --auth-digest-sz 12 --total-ops 10000000 --burst-sz 32 --buffer-sz 64 Signed-off-by: Declan Doherty <declan.doherty@intel.com> Signed-off-by: Slawomir Mrozowicz <slawomirx.mrozowicz@intel.com> Signed-off-by: Piotr Azarewicz <piotrx.t.azarewicz@intel.com> Signed-off-by: Marcin Kerlin <marcinx.kerlin@intel.com> Signed-off-by: Michal Kobylinski <michalx.kobylinski@intel.com>
2017-01-25 16:27:33 +00:00
Crypto performance test application
M: Declan Doherty <declan.doherty@intel.com>
maintainers: set git tree for test applications Changes on the main test applications should be considered against subtrees where most of the API changes and development happen: - testpmd goes through dpdk-next-net as it is mainly about ethdev, - dpdk-test-compress-perf goes through dpdk-next-crypto since the compress API goes through this tree, - dpdk-test-crypto-perf through dpdk-next-crypto, - dpdk-test-eventdev through dpdk-next-eventdev, Signed-off-by: David Marchand <david.marchand@redhat.com> Acked-by: Jerin Jacob <jerinj@marvell.com> Acked-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Andrew Rybchenko <arybchenko@solarflare.com> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
2020-01-14 09:18:15 +00:00
T: git://dpdk.org/next/dpdk-next-crypto
app/crypto-perf: introduce performance test application This patchset introduce new application which allows measuring performance parameters of PMDs available in crypto tree. The goal of this application is to replace existing performance tests in app/test. Parameters available are: throughput (--ptest throughput) and latency (--ptest latency). User can use multiply cores to run tests on but only one type of crypto PMD can be measured during single application execution. Cipher parameters, type of device, type of operation and chain mode have to be specified in the command line as application parameters. These parameters are checked using device capabilities structure. Couple of new library functions in librte_cryptodev are introduced for application use. To build the application a CONFIG_RTE_APP_CRYPTO_PERF flag has to be set (it is set by default). Example of usage: -c 0xc0 --vdev crypto_aesni_mb_pmd -w 0000:00:00.0 -- --ptest throughput --devtype crypto_aesni_mb --optype cipher-then-auth --cipher-algo aes-cbc --cipher-op encrypt --cipher-key-sz 16 --auth-algo sha1-hmac --auth-op generate --auth-key-sz 64 --auth-digest-sz 12 --total-ops 10000000 --burst-sz 32 --buffer-sz 64 Signed-off-by: Declan Doherty <declan.doherty@intel.com> Signed-off-by: Slawomir Mrozowicz <slawomirx.mrozowicz@intel.com> Signed-off-by: Piotr Azarewicz <piotrx.t.azarewicz@intel.com> Signed-off-by: Marcin Kerlin <marcinx.kerlin@intel.com> Signed-off-by: Michal Kobylinski <michalx.kobylinski@intel.com>
2017-01-25 16:27:33 +00:00
F: app/test-crypto-perf/
doc: describe new performance test application Add documentation to describe using the new performance test application. Signed-off-by: Slawomir Mrozowicz <slawomirx.mrozowicz@intel.com> Signed-off-by: Piotr Azarewicz <piotrx.t.azarewicz@intel.com>
2017-01-25 16:27:35 +00:00
F: doc/guides/tools/cryptoperf.rst
app/crypto-perf: introduce performance test application This patchset introduce new application which allows measuring performance parameters of PMDs available in crypto tree. The goal of this application is to replace existing performance tests in app/test. Parameters available are: throughput (--ptest throughput) and latency (--ptest latency). User can use multiply cores to run tests on but only one type of crypto PMD can be measured during single application execution. Cipher parameters, type of device, type of operation and chain mode have to be specified in the command line as application parameters. These parameters are checked using device capabilities structure. Couple of new library functions in librte_cryptodev are introduced for application use. To build the application a CONFIG_RTE_APP_CRYPTO_PERF flag has to be set (it is set by default). Example of usage: -c 0xc0 --vdev crypto_aesni_mb_pmd -w 0000:00:00.0 -- --ptest throughput --devtype crypto_aesni_mb --optype cipher-then-auth --cipher-algo aes-cbc --cipher-op encrypt --cipher-key-sz 16 --auth-algo sha1-hmac --auth-op generate --auth-key-sz 64 --auth-digest-sz 12 --total-ops 10000000 --burst-sz 32 --buffer-sz 64 Signed-off-by: Declan Doherty <declan.doherty@intel.com> Signed-off-by: Slawomir Mrozowicz <slawomirx.mrozowicz@intel.com> Signed-off-by: Piotr Azarewicz <piotrx.t.azarewicz@intel.com> Signed-off-by: Marcin Kerlin <marcinx.kerlin@intel.com> Signed-off-by: Michal Kobylinski <michalx.kobylinski@intel.com>
2017-01-25 16:27:33 +00:00
app/testeventdev: introduce dpdk-test-eventdev app The dpdk-test-eventdev tool is a Data Plane Development Kit (DPDK) application that allows exercising various eventdev use cases. This application has a generic framework to add new eventdev based test cases to verify functionality and measure the performance parameters of DPDK eventdev devices. This patch adds the skeleton of the dpdk-test-eventdev application. Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
2017-07-04 04:52:56 +00:00
Eventdev test application
maintainers: update Cavium email ids Following Marvell's acquisition of Cavium, we need to update all the Cavium maintainer's entries to point to our new e-mail addresses. Update maintainers as they are no longer working for Cavium. Thanks to Harish Patil for his support and development of our various dpdk drivers. Signed-off-by: Jerin Jacob <jerinj@marvell.com>
2018-12-16 15:43:25 +00:00
M: Jerin Jacob <jerinj@marvell.com>
maintainers: set git tree for test applications Changes on the main test applications should be considered against subtrees where most of the API changes and development happen: - testpmd goes through dpdk-next-net as it is mainly about ethdev, - dpdk-test-compress-perf goes through dpdk-next-crypto since the compress API goes through this tree, - dpdk-test-crypto-perf through dpdk-next-crypto, - dpdk-test-eventdev through dpdk-next-eventdev, Signed-off-by: David Marchand <david.marchand@redhat.com> Acked-by: Jerin Jacob <jerinj@marvell.com> Acked-by: Thomas Monjalon <thomas@monjalon.net> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Andrew Rybchenko <arybchenko@solarflare.com> Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
2020-01-14 09:18:15 +00:00
T: git://dpdk.org/next/dpdk-next-eventdev
app/testeventdev: introduce dpdk-test-eventdev app The dpdk-test-eventdev tool is a Data Plane Development Kit (DPDK) application that allows exercising various eventdev use cases. This application has a generic framework to add new eventdev based test cases to verify functionality and measure the performance parameters of DPDK eventdev devices. This patch adds the skeleton of the dpdk-test-eventdev application. Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
2017-07-04 04:52:56 +00:00
F: app/test-eventdev/
doc: describe the new eventdev test application Add documentation to describe usage of eventdev test application and supported command line arguments. Signed-off-by: Guduri Prathyusha <gprathyusha@caviumnetworks.com> Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Acked-by: Harry van Haaren <harry.van.haaren@intel.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2017-07-04 04:53:23 +00:00
F: doc/guides/tools/testeventdev.rst
doc: add order queue test in eventdev test guide Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Signed-off-by: Guduri Prathyusha <gprathyusha@caviumnetworks.com> Acked-by: John McNamara <john.mcnamara@intel.com> Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
2017-07-04 04:53:24 +00:00
F: doc/guides/tools/img/eventdev_*
test: move to app directory Since all other apps have been moved to the "app" folder, the autotest app remains alone in the test folder. Rather than having an entire top-level folder for this, we can move it back to where it all started in early versions of DPDK - the "app/" folder. This move has a couple of advantages: * This reduces clutter at the top level of the project, due to one less folder. * It eliminates the separate build task necessary for building the autotests using make "make test-build" which means that developers are less likely to miss something in their own compilation tests * It re-aligns the final location of the test binary in the app folder when building with make with it's location in the source tree. For meson builds, the autotest app is different from the other apps in that it needs a series of different test cases defined for it for use by "meson test". Therefore, it does not get built as part of the main loop in the app folder, but gets built separately at the end. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
2019-02-26 12:19:03 +00:00
F: app/test/test_event_ring.c
app/testeventdev: introduce dpdk-test-eventdev app The dpdk-test-eventdev tool is a Data Plane Development Kit (DPDK) application that allows exercising various eventdev use cases. This application has a generic framework to add new eventdev based test cases to verify functionality and measure the performance parameters of DPDK eventdev devices. This patch adds the skeleton of the dpdk-test-eventdev application. Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
2017-07-04 04:52:56 +00:00
maintainers: update procinfo maintainer Update procinfo maintainer and name of the application. Signed-off-by: John McNamara <john.mcnamara@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2016-11-18 17:09:26 +00:00
Procinfo tool
app: replace dump_cfg by proc_info proc_info displays statistics information including extended stats for given DPDK ports and dumps the memory information for DPDK. Signed-off-by: Maryam Tahhan <maryam.tahhan@intel.com> Acked-by: Olivier Matz <olivier.matz@6wind.com>
2015-07-15 13:11:32 +00:00
M: Maryam Tahhan <maryam.tahhan@intel.com>
maintainers: update procinfo maintainer Update procinfo maintainer and name of the application. Signed-off-by: John McNamara <john.mcnamara@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2016-11-18 17:09:26 +00:00
M: Reshma Pattan <reshma.pattan@intel.com>
app/procinfo: rename folder to remove underscore All other apps in the app folder use "-" rather than "_" to separate words in the app name, so rename proc_info to be consistent. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
2018-02-16 16:53:35 +00:00
F: app/proc-info/
doc: move tool guides in their own subdirectory This is to clarify the scope of these documents that are more tools than sample applications. Also this is a preparation step to add more tools and generate man pages off of their rst files. Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com> Acked-by: Luca Boccassi <lboccass@brocade.com> Acked-by: John McNamara <john.mcnamara@intel.com>
2016-08-31 07:50:09 +00:00
F: doc/guides/tools/proc_info.rst
app: replace dump_cfg by proc_info proc_info displays statistics information including extended stats for given DPDK ports and dumps the memory information for DPDK. Signed-off-by: Maryam Tahhan <maryam.tahhan@intel.com> Acked-by: Olivier Matz <olivier.matz@6wind.com>
2015-07-15 13:11:32 +00:00
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
Other Example Applications
--------------------------
examples/ethtool: add user-space ethtool sample application Further enhancements to the userspace ethtool implementation that was submitted in 2.1 and packaged as a self-contained sample application. Implements an rte_ethtool shim layer based on rte_ethdev API, along with a command prompt driven demonstration application. Signed-off-by: Remy Horton <remy.horton@intel.com>
2015-12-07 13:48:59 +00:00
F: examples/ethtool/
F: doc/guides/sample_app_ug/ethtool.rst
examples/fips_validation: add crypto FIPS application Added FIPS application into the examples to allow users to use a simple sample app to validate their systems and be able to get FIPS certification. Signed-off-by: Marko Kovacevic <marko.kovacevic@intel.com> Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com> Acked-by: Arek Kusztal <arkadiuszx.kusztal@intel.com> Reviewed-by: Akhil Goyal <akhil.goyal@nxp.com>
2018-11-02 09:55:28 +00:00
M: Marko Kovacevic <marko.kovacevic@intel.com>
F: examples/fips_validation/
F: doc/guides/sample_app_ug/fips_validation.rst
examples/flow_filtering: add simple demo of flow API This application shows a simple usage of the rte_flow API for hardware filtering offloading. In this demo we are filtering specific IP to specific target queue, while sending all the rest of the packets to other queue. Signed-off-by: Ori Kam <orika@mellanox.com>
2017-11-01 09:42:37 +00:00
M: Ori Kam <orika@mellanox.com>
F: examples/flow_filtering/
F: doc/guides/sample_app_ug/flow_filtering.rst
maintainers: claim misc sample applications Claim the following sample applications: * dpdk_qat * helloworld * l2fwd * skeleton Signed-off-by: Bruce Richardson <bruce.richarsdon@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-03-11 10:48:07 +00:00
M: Bruce Richardson <bruce.richardson@intel.com>
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: examples/helloworld/
F: doc/guides/sample_app_ug/hello_world.rst
maintainers: update for IPsec application Signed-off-by: Radu Nicolau <radu.nicolau@intel.com> Acked-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
2017-10-18 12:06:15 +00:00
M: Radu Nicolau <radu.nicolau@intel.com>
maintainers: update for ipsec-secgw Signed-off-by: Akhil Goyal <akhil.goyal@nxp.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2018-01-18 11:20:47 +00:00
M: Akhil Goyal <akhil.goyal@nxp.com>
examples/ipsec-secgw: add IPsec sample application Sample app implementing an IPsec Security Geteway. The main goal of this app is to show the use of cryptodev framework in a "real world" application. Currently only supported static IPv4 ESP IPsec tunnels for the following algorithms: - Cipher: AES-CBC, NULL - Authentication: HMAC-SHA1, NULL Not supported: - SA auto negotiation (No IKE implementation) - chained mbufs Signed-off-by: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2016-03-11 02:12:40 +00:00
F: examples/ipsec-secgw/
F: doc/guides/sample_app_ug/ipsec_secgw.rst
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: examples/ipv4_multicast/
F: doc/guides/sample_app_ug/ipv4_multicast.rst
maintainers: claim misc sample applications Claim the following sample applications: * dpdk_qat * helloworld * l2fwd * skeleton Signed-off-by: Bruce Richardson <bruce.richarsdon@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-03-11 10:48:07 +00:00
M: Bruce Richardson <bruce.richardson@intel.com>
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: examples/l2fwd/
F: doc/guides/sample_app_ug/l2_forward_real_virtual.rst
maintainers: sort examples Keep sorting examples and fix l2fwd-cat path. Fixes: ab129e9065a5 ("examples/ptpclient: add minimal PTP client") Fixes: f6baccbc2b3b ("examples/l2fwd-cat: add sample application for PQoS CAT and CDP") Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2016-03-22 09:59:52 +00:00
M: Tomasz Kantecki <tomasz.kantecki@intel.com>
F: doc/guides/sample_app_ug/l2_forward_cat.rst
F: examples/l2fwd-cat/
examples/l2fwd-event: add default poll mode routines Add the default l2fwd poll mode routines similar to examples/l2fwd. Signed-off-by: Sunil Kumar Kori <skori@marvell.com> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com> Acked-by: Nipun Gupta <nipun.gupta@nxp.com> Acked-by: Jerin Jacob <jerinj@marvell.com>
2019-10-30 16:26:42 +00:00
M: Sunil Kumar Kori <skori@marvell.com>
M: Pavan Nikhilesh <pbhagavatula@marvell.com>
T: git://dpdk.org/next/dpdk-next-eventdev
F: examples/l2fwd-event/
doc: add application usage guide for l2fwd-event Add documentation for l2fwd-event example. Update release notes. Signed-off-by: Sunil Kumar Kori <skori@marvell.com> Acked-by: Nipun Gupta <nipun.gupta@nxp.com> Acked-by: Jerin Jacob <jerinj@marvell.com>
2019-10-30 17:03:47 +00:00
F: doc/guides/sample_app_ug/l2_forward_event.rst
examples/l2fwd-event: add default poll mode routines Add the default l2fwd poll mode routines similar to examples/l2fwd. Signed-off-by: Sunil Kumar Kori <skori@marvell.com> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com> Acked-by: Nipun Gupta <nipun.gupta@nxp.com> Acked-by: Jerin Jacob <jerinj@marvell.com>
2019-10-30 16:26:42 +00:00
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: examples/l3fwd/
F: doc/guides/sample_app_ug/l3_forward.rst
F: examples/link_status_interrupt/
F: doc/guides/sample_app_ug/link_status_intr.rst
examples/performance-thread: mark as experimental This commit removes the performance thread example from examples/Makefile, and marks the example as "experimental" in the release note, and it its API headers files. Signed-off-by: Ian Betts <ian.betts@intel.com>
2015-12-10 12:24:58 +00:00
L-threads - EXPERIMENTAL
maintainers: replace lthreads maintainer Signed-off-by: John McNamara <john.mcnamara@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2016-11-18 17:09:51 +00:00
M: John McNamara <john.mcnamara@intel.com>
examples/performance-thread: add l3fwd-thread app This commit adds an L3 forwarding application to the performace-thread example. Signed-off-by: Ian Betts <ian.betts@intel.com> Acked-by: Tomasz Kulasek <tomaszx.kulasek@intel.com>
2015-12-08 06:05:16 +00:00
F: examples/performance-thread/
F: doc/guides/sample_app_ug/performance_thread.rst
maintainers: claim maintainership of ptpclient example Claim maintainership of examples/ptpclient/ Signed-off-by: Kirill Rybalchenko <kirill.rybalchenko@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2019-10-15 13:45:35 +00:00
M: Kirill Rybalchenko <kirill.rybalchenko@intel.com>
maintainers: sort examples Keep sorting examples and fix l2fwd-cat path. Fixes: ab129e9065a5 ("examples/ptpclient: add minimal PTP client") Fixes: f6baccbc2b3b ("examples/l2fwd-cat: add sample application for PQoS CAT and CDP") Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2016-03-22 09:59:52 +00:00
F: examples/ptpclient/
examples/rxtx_callbacks: show use of callbacks Example showing how callbacks can be used to insert a timestamp into each packet on RX. On TX the timestamp is used to calculate the packet latency through the app, in cycles. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Signed-off-by: John McNamara <john.mcnamara@intel.com> Acked-by: Declan Doherty <declan.doherty@intel.com>
2015-02-23 18:30:10 +00:00
M: Bruce Richardson <bruce.richardson@intel.com>
M: John McNamara <john.mcnamara@intel.com>
F: examples/rxtx_callbacks/
doc: add Rx and Tx callbacks sample app user guide Added a sample application guide for the rxtx_callbacks app. Signed-off-by: John McNamara <john.mcnamara@intel.com> Acked-by: Siobhan Butler <siobhan.a.butler@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2015-02-25 19:46:02 +00:00
F: doc/guides/sample_app_ug/rxtx_callbacks.rst
examples/rxtx_callbacks: show use of callbacks Example showing how callbacks can be used to insert a timestamp into each packet on RX. On TX the timestamp is used to calculate the packet latency through the app, in cycles. Signed-off-by: Bruce Richardson <bruce.richardson@intel.com> Signed-off-by: John McNamara <john.mcnamara@intel.com> Acked-by: Declan Doherty <declan.doherty@intel.com>
2015-02-23 18:30:10 +00:00
examples/service_cores: add new sample application This commit adds a new sample app, which showcases the value of running services. In particular it allows the application to dynamically schedule services to service-cores. The sample app itself registers a number of dummy services, and applies different profiles to them at runtime. Note that this sample application does not forward any traffic - it demonstrates advanced usage of the service cores API. Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com> Acked-by: Gage Eads <gage.eads@intel.com>
2017-10-19 10:31:11 +00:00
M: Harry van Haaren <harry.van.haaren@intel.com>
F: examples/service_cores/
F: doc/guides/sample_app_ug/service_cores.rst
maintainers: claim misc sample applications Claim the following sample applications: * dpdk_qat * helloworld * l2fwd * skeleton Signed-off-by: Bruce Richardson <bruce.richarsdon@intel.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
2015-03-11 10:48:07 +00:00
M: Bruce Richardson <bruce.richardson@intel.com>
doc: add basic forwarding skeleton user guide Added a sample application guide for the basic forwarding /skeleton app. Signed-off-by: John McNamara <john.mcnamara@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2015-02-25 19:46:01 +00:00
M: John McNamara <john.mcnamara@intel.com>
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: examples/skeleton/
doc: add basic forwarding skeleton user guide Added a sample application guide for the basic forwarding /skeleton app. Signed-off-by: John McNamara <john.mcnamara@intel.com> Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
2015-02-25 19:46:01 +00:00
F: doc/guides/sample_app_ug/skeleton.rst
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
maintainers: update for tep_termination example Xiaoyun Li has agreed to take over the maintainership of example application tep_termination, as Jijiang Liu is no longer working on that. Signed-off-by: Helin Zhang <helin.zhang@intel.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
2018-06-22 09:13:59 +00:00
M: Xiaoyun Li <xiaoyun.li@intel.com>
examples/tep_term: initialize VXLAN sample This patch creates the virtio devices management mechanism. These functions are from the vHost example, which include: - virtio device creation. - virtio device destroying. - virtio device maintenance. Signed-off-by: Jijiang Liu <jijiang.liu@intel.com> [Thomas: remove unused function validate_nb_devices()] [Thomas: add maintainers section]
2015-06-22 16:40:56 +00:00
F: examples/tep_termination/
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: examples/vmdq/
doc: add user guide for VMDq example Currently, there is no documentation for VMDq example, this path added the user guide for VMDq. Signed-off-by: Junyu Jiang <junyux.jiang@intel.com> Reviewed-by: Jingjing Wu <jingjing.wu@intel.com>
2020-03-25 06:32:47 +00:00
F: doc/guides/sample_app_ug/vmdq_forwarding.rst
maintainers: start a Linux-style file This MAINTAINERS file is inspired from the Linux one. Almost all files are split into areas in order to identify maintainers of each DPDK area. Note that a maintainer is not a git tree manager. Candidates are welcome to send a patch to sign up for one or several areas. There is a script to check coverage, especially when adding or moving files. Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Neil Horman <nhorman@tuxdriver.com>
2015-01-23 12:31:59 +00:00
F: examples/vmdq_dcb/
F: doc/guides/sample_app_ug/vmdq_dcb_forwarding.rst
Reference in New Issue Copy Permalink