On 2/16/2023 12:30 AM, Mingxia Liu wrote:
> Add support of AVX512 data path for split queue model.
>
> Signed-off-by: Wenjun Wu <wenjun1...@intel.com>
> Signed-off-by: Mingxia Liu <mingxia....@intel.com>
<...>
> diff --git a/drivers/net/cpfl/meson.build b/drivers/net/cpfl/meson.build
> index fbe6500826..2cf69258e2 100644
> --- a/drivers/net/cpfl/meson.build
> +++ b/drivers/net/cpfl/meson.build
> @@ -23,13 +23,15 @@ sources = files(
> if arch_subdir == 'x86'
> cpfl_avx512_cpu_support = (
> cc.get_define('__AVX512F__', args: machine_args) != '' and
> - cc.get_define('__AVX512BW__', args: machine_args) != ''
> + cc.get_define('__AVX512BW__', args: machine_args) != '' and
> + cc.get_define('__AVX512DQ__', args: machine_args) != ''
> )
>
> cpfl_avx512_cc_support = (
> not machine_args.contains('-mno-avx512f') and
> cc.has_argument('-mavx512f') and
> - cc.has_argument('-mavx512bw')
> + cc.has_argument('-mavx512bw') and
> + cc.has_argument('-mavx512dq')
> )
+Bruce
Does it make sense to have a common 'avx512_cc_support' meson function
that all required drivers and libraries to use?
As it is getting more complex to detect and it is required by multiple
components.
