|
Revision tags: v22.03, v22.03-rc4, v22.03-rc3, v22.03-rc2, v22.03-rc1, v21.11, v21.11-rc4, v21.11-rc3, v21.11-rc2, v21.11-rc1, v21.08, v21.08-rc4, v21.08-rc3, v21.08-rc2, v21.08-rc1, v21.05, v21.05-rc4, v21.05-rc3, v21.05-rc2, v21.05-rc1, v21.02, v21.02-rc4, v21.02-rc3, v21.02-rc2, v21.02-rc1, v20.11, v20.11-rc5, v20.11-rc4, v20.11-rc3, v20.11-rc2, v20.11-rc1 |
|
| #
d9739192 |
| 19-Aug-2020 |
Wei Hu (Xavier) <[email protected]> |
test/cpuflags: add new Arm flags
This patch adds new flags into the test_cpuflags() functions for ARM64 platform, such as RTE_CPUFLAG_SVE, etc.
Signed-off-by: Wei Hu (Xavier) <[email protected]
test/cpuflags: add new Arm flags
This patch adds new flags into the test_cpuflags() functions for ARM64 platform, such as RTE_CPUFLAG_SVE, etc.
Signed-off-by: Wei Hu (Xavier) <[email protected]> Reviewed-by: Ruifeng Wang <[email protected]>
show more ...
|
| #
e9b97392 |
| 11-Sep-2020 |
Ruifeng Wang <[email protected]> |
config: remap flags used for Arm platforms
RTE_ARCH_xx flags are used to distinguish platform architectures. These flags can be used to pick different code paths for different architectures at compi
config: remap flags used for Arm platforms
RTE_ARCH_xx flags are used to distinguish platform architectures. These flags can be used to pick different code paths for different architectures at compile time. For Arm platforms, there are 3 flags in use: RTE_ARCH_ARM, RTE_ARCH_ARMv7 and RTE_ARCH_ARM64. RTE_ARCH_ARM64 is for 64-bit aarch64 platforms, and RTE_ARCH_ARM & RTE_ARCH_ARMv7 are for 32-bit platforms. RTE_ARCH_ARMv7 is for ARMv7 platforms as its name suggested.
The issue is meaning of RTE_ARCH_ARM is not clear enough. Because no info about platform word length is included in the name. To make the flag names more clear, a naming scheme is proposed.
RTE_ARCH_ARM (all Arm platforms) | +----RTE_ARCH_32 (New. 32-bit platforms of all architectures) | | | +----RTE_ARCH_ARMv7 (ARMv7 platforms) | | | +----RTE_ARCH_ARMv8_AARCH32 (aarch32 state on aarch64 machine) | +----RTE_ARCH_64 (64-bit platforms of all architectures) | +----RTE_ARCH_ARM64 (64-bit Arm platforms)
RTE_ARCH_32 will be explicitly defined for 32-bit platforms.
To fit into the new naming scheme, current usage of RTE_ARCH_ARM in project is mapped to (RTE_ARCH_ARM && RTE_ARCH_32).
Matching flags for other architectures are: RTE_ARCH_X86 | +----RTE_ARCH_32 | | | +----RTE_ARCH_I686 | | | +----RTE_ARCH_X86_X32 | +----RTE_ARCH_64 | +----RTE_ARCH_X86_64
RTE_ARCH_PPC_64 ---- RTE_ARCH_64
Signed-off-by: Ruifeng Wang <[email protected]> Reviewed-by: Phil Yang <[email protected]>
show more ...
|
|
Revision tags: v20.08, v20.08-rc4, v20.08-rc3, v20.08-rc2, v20.08-rc1, v20.05, v20.05-rc4, v20.05-rc3, v20.05-rc2, v20.05-rc1, v20.02, v20.02-rc4, v20.02-rc3, v20.02-rc2, v20.02-rc1, v19.11, v19.11-rc4, v19.11-rc3, v19.11-rc2, v19.11-rc1, v19.08, v19.08-rc4, v19.08-rc3, v19.08-rc2, v19.08-rc1, v19.05, v19.05-rc4, v19.05-rc3, v19.05-rc2, v19.05-rc1 |
|
| #
a9de470c |
| 26-Feb-2019 |
Bruce Richardson <[email protected]> |
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 ca
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 <[email protected]>
show more ...
|
|
Revision tags: v19.02, v19.02-rc4, v19.02-rc3, v19.02-rc2, v19.02-rc1, v18.11, v18.11-rc5, v18.11-rc4, v18.11-rc3, v18.11-rc2, v18.11-rc1, v18.08, v18.08-rc3, v18.08-rc2, v18.08-rc1, v18.05, v18.05-rc6, v18.05-rc5, v18.05-rc4, v18.05-rc3, v18.05-rc2, v18.05-rc1, v18.02, v18.02-rc4, v18.02-rc3, v18.02-rc2, v18.02-rc1, v17.11, v17.11-rc4, v17.11-rc3, v17.11-rc2, v17.11-rc1, v17.08, v17.08-rc4, v17.08-rc3, v17.08-rc2, v17.08-rc1, v17.05, v17.05-rc4, v17.05-rc3, v17.05-rc2, v17.05-rc1, v17.02, v17.02-rc3, v17.02-rc2, v17.02-rc1, v16.11, v16.11-rc3, v16.11-rc2, v16.11-rc1, v16.07, v16.07-rc5, v16.07-rc4, v16.07-rc3 |
|
| #
26e09db6 |
| 13-Jul-2016 |
Thomas Monjalon <[email protected]> |
app/test: rework command registration
The tests are registered with their command name by adding a structure to a list. The structure of each test was declared in each test file and passed to the re
app/test: rework command registration
The tests are registered with their command name by adding a structure to a list. The structure of each test was declared in each test file and passed to the register macro. This rework generate the structure inside the register macro.
Signed-off-by: Thomas Monjalon <[email protected]> Reviewed-by: Jan Viktorin <[email protected]>
show more ...
|
|
Revision tags: v16.07-rc2, v16.07-rc1, v16.04, v16.04-rc4, v16.04-rc3, v16.04-rc2, v16.04-rc1 |
|
| #
716bf820 |
| 02-Mar-2016 |
Jerin Jacob <[email protected]> |
eal/arm: check support of armv8.1 atomics
armv8.1 adds support for new atomic instructions. Linux kernel v4.3 onwards, the presence of atomic instruction support can detect through HWCAP_ATOMICS
Si
eal/arm: check support of armv8.1 atomics
armv8.1 adds support for new atomic instructions. Linux kernel v4.3 onwards, the presence of atomic instruction support can detect through HWCAP_ATOMICS
Signed-off-by: Jerin Jacob <[email protected]> Reviewed-by: Jan Viktorin <[email protected]>
show more ...
|
|
Revision tags: v2.2.0, v2.2.0-rc4, v2.2.0-rc3, v2.2.0-rc2 |
|
| #
97523f82 |
| 06-Nov-2015 |
Jerin Jacob <[email protected]> |
eal/arm: add CPU flags for ARMv8
Signed-off-by: Jerin Jacob <[email protected]>
|
|
Revision tags: v2.2.0-rc1 |
|
| #
b94e5c94 |
| 02-Nov-2015 |
Vlastimil Kosar <[email protected]> |
eal/arm: add CPU flags for ARMv7
This implementation is based on IBM POWER version of rte_cpuflags. We use software emulation of HW capability registers, because those are usually not directly acces
eal/arm: add CPU flags for ARMv7
This implementation is based on IBM POWER version of rte_cpuflags. We use software emulation of HW capability registers, because those are usually not directly accessible from userspace on ARM.
Signed-off-by: Vlastimil Kosar <[email protected]> Signed-off-by: Jan Viktorin <[email protected]> Acked-by: David Marchand <[email protected]>
show more ...
|
|
Revision tags: v2.1.0, v2.1.0-rc4, v2.1.0-rc3, v2.1.0-rc2, v2.1.0-rc1 |
|
| #
f7f500d2 |
| 09-Jul-2015 |
Cyril Chemparathy <[email protected]> |
app/test: restrict x86 cpu flags checks to x86 builds
The original code mistakenly defaulted to X86 when RTE_ARCH_PPC_64 was left undefined. This did not accommodate other non-PPC/non-X86 architect
app/test: restrict x86 cpu flags checks to x86 builds
The original code mistakenly defaulted to X86 when RTE_ARCH_PPC_64 was left undefined. This did not accommodate other non-PPC/non-X86 architectures. This patch fixes this issue.
Signed-off-by: Cyril Chemparathy <[email protected]> Signed-off-by: Zhigang Lu <[email protected]> Acked-by: Bruce Richardson <[email protected]>
show more ...
|
|
Revision tags: v2.0.0, v2.0.0-rc3, v2.0.0-rc2, v2.0.0-rc1, v1.8.0, v1.8.0-rc6, v1.8.0-rc5, v1.8.0-rc4, v1.8.0-rc3, v1.8.0-rc2 |
|
| #
9ae15538 |
| 25-Nov-2014 |
Chao Zhu <[email protected]> |
eal/ppc: cpu flag checks for IBM Power
IBM Power processor doesn't have CPU flag hardware registers. This patch uses aux vector software register to get CPU flags and add CPU flag checking support f
eal/ppc: cpu flag checks for IBM Power
IBM Power processor doesn't have CPU flag hardware registers. This patch uses aux vector software register to get CPU flags and add CPU flag checking support for IBM Power architecture.
Signed-off-by: Chao Zhu <[email protected]> Acked-by: David Marchand <[email protected]>
show more ...
|
|
Revision tags: v1.8.0-rc1, v1.7.1 |
|
| #
942405f9 |
| 18-Aug-2014 |
David Marchand <[email protected]> |
app/test: convert all tests to register system
Remove all tests from the builtin commands list and use the dynamic commands list register macro.
Signed-off-by: David Marchand <david.marchand@6wind.
app/test: convert all tests to register system
Remove all tests from the builtin commands list and use the dynamic commands list register macro.
Signed-off-by: David Marchand <[email protected]> Acked-by: Bruce Richardson <[email protected]> Acked-by: Neil Horman <[email protected]>
show more ...
|
|
Revision tags: v1.7.0, v1.7.0-rc4, v1.7.0-rc3, v1.7.0-rc2, v1.7.0-rc1 |
|
| #
3031749c |
| 03-Jun-2014 |
Bruce Richardson <[email protected]> |
remove trailing whitespaces
This commit removes trailing whitespace from lines in files. Almost all files are affected, as the BSD license copyright header had trailing whitespace on 4 lines in it [
remove trailing whitespaces
This commit removes trailing whitespace from lines in files. Almost all files are affected, as the BSD license copyright header had trailing whitespace on 4 lines in it [hence the number of files reporting 8 lines changed in the diffstat].
Signed-off-by: Bruce Richardson <[email protected]> Acked-by: Neil Horman <[email protected]> [Thomas: remove spaces before tabs in libs] [Thomas: remove more trailing spaces in non-C files] Signed-off-by: Thomas Monjalon <[email protected]>
show more ...
|
|
Revision tags: v1.6.0r2, v1.6.0r1, v1.6.0r0, v1.5.2r2, v1.5.2r1, v1.5.2r0, v1.5.1r2, v1.5.1r1, v1.5.1r0, v1.5.0r2 |
|
| #
21a7f4e2 |
| 14-Nov-2013 |
Thomas Monjalon <[email protected]> |
app/test: fix build without librte_cmdline
Some features are not available if LIBRTE_CMDLINE is disabled: - interactive commands - cmdline tests Remove also cmdline_parse includes which are not need
app/test: fix build without librte_cmdline
Some features are not available if LIBRTE_CMDLINE is disabled: - interactive commands - cmdline tests Remove also cmdline_parse includes which are not needed.
Signed-off-by: Thomas Monjalon <[email protected]> Acked-by: Olivier Matz <[email protected]>
show more ...
|
| #
e9d48c00 |
| 10-Feb-2014 |
Bruce Richardson <[email protected]> |
update Intel copyright years to 2014
Signed-off-by: Bruce Richardson <[email protected]>
|
|
Revision tags: v1.4.1r2, v1.5.0r1, v1.5.0r0 |
|
| #
1c1d4d7a |
| 18-Sep-2013 |
Intel <intel.com> |
doc: whitespace changes in licenses
Signed-off-by: Intel
|
|
Revision tags: v1.4.1r1, v1.4.1r0, v1.4.0r0, v1.3.1r3, v1.3.1r2, v1.3.1r1, v1.3.1r0, v1.3.0r0, v1.2.3r4, v1.2.3r3, v1.2.3r2, v1.2.3r1 |
|
| #
b6df9fc8 |
| 12-Mar-2013 |
Intel <intel.com> |
update copyright date to 2013
Signed-off-by: Intel
|
|
Revision tags: v1.2.3r0 |
|
| #
dada9ef6 |
| 19-Dec-2012 |
Intel <intel.com> |
remove version in all files
Signed-off-by: Intel
|
| #
af75078f |
| 04-Sep-2012 |
Intel <intel.com> |
first public release
version 1.2.3
Signed-off-by: Intel
|