RE: [PATCH v5 00/11] remove component-specific logic for AVX builds

2025-06-08 Thread Varghese, Vipin
[Public] Snipped > > > > A number of libs and drivers had special optimized AVX2 and AVX512 > > code paths for performance reasons, and these tended to have > > copy-pasted logic to build those files. Centralise that logic in the > > main drivers/ and lib/ meson.build files to avoid duplication.

Re: [PATCH v5 00/11] remove component-specific logic for AVX builds

2025-03-26 Thread David Marchand
On Tue, Mar 25, 2025 at 5:03 PM Bruce Richardson wrote: > > A number of libs and drivers had special optimized AVX2 and AVX512 code > paths for performance reasons, and these tended to have copy-pasted > logic to build those files. Centralise that logic in the main > drivers/ and lib/ meson.build

RE: [PATCH v5 00/11] remove component-specific logic for AVX builds

2025-03-26 Thread Konstantin Ananyev
> A number of libs and drivers had special optimized AVX2 and AVX512 code > paths for performance reasons, and these tended to have copy-pasted > logic to build those files. Centralise that logic in the main > drivers/ and lib/ meson.build files to avoid duplication. > > v5: fix RTE_ARCH_X86 ma

[PATCH v5 00/11] remove component-specific logic for AVX builds

2025-03-25 Thread Bruce Richardson
A number of libs and drivers had special optimized AVX2 and AVX512 code paths for performance reasons, and these tended to have copy-pasted logic to build those files. Centralise that logic in the main drivers/ and lib/ meson.build files to avoid duplication. v5: fix RTE_ARCH_X86 macro, which brok