[dpdk-dev] [PATCH v9 00/14] Arm build options rework

Jerin Jacob jerinjacobk at gmail.com
Thu Nov 12 18:00:38 CET 2020


On Wed, Nov 11, 2020 at 6:48 PM Juraj Linkeš <juraj.linkes at pantheon.tech> wrote:
>
> The current way of specifying Arm configuration options is insufficient
> since we can't identify the SoC we're building for from the MIDR
> information. For example, we can't distinguish between N1SDP, Graviton2
> or Ampere Altra.
>
> Add a way to specify the cpu count and numa node count for cross builds
> and aarch64 -> aarch64 (SoC) builds.
>
> We also want to be able to disable which drivers (and possibly
> libraries) are built without user input. This is useful when building:
> 1. on an SoC that is slow and we want to build only what is necessary
>   without the user having to check which libraries they have installed
> 2. a cross build on a fast aarch64 machine but with target SoC which
>   differs in capabilities or libraries.
> This is achieved by specifying the drivers in SoC configuration.
>
> Among libraries, only libnuma can be now disabled.
>
> Also add an optional way to discover cpu count a numa node count. Fix
> -Dmax_lcores and -Dmax_numa_nodes for arm builds.


Series Acked-by: Jerin Jacob <jerinj at marvell.com>
Series Tested-by: Jerin Jacob <jerinj at marvell.com>

# Verified the mcpu and cache line aspects of generic an octeontx2 build
# Test the performance of build. No regression see with testpmd,
l2fwd, and l3fwd,

I would suggest merging this for RC4. Additional features/enhancements
can be done in 21.02 for release.


More information about the dev mailing list