On Wed, Jan 29, 2025 at 05:48:56PM +0530, Shaiq Wani wrote: > updated the documentation to reflect that both AVX512 and AVX2 > support are available. > > Signed-off-by: Shaiq Wani <shaiq.w...@intel.com> > --- > doc/guides/nics/idpf.rst | 7 +++---- > 1 file changed, 3 insertions(+), 4 deletions(-) > > diff --git a/doc/guides/nics/idpf.rst b/doc/guides/nics/idpf.rst > index 0370989a07..3738d0d91a 100644 > --- a/doc/guides/nics/idpf.rst > +++ b/doc/guides/nics/idpf.rst > @@ -92,10 +92,9 @@ Vector path for Rx and Tx path are selected automatically. > The paths are chosen based on 2 conditions: > > - ``CPU`` > - > - On the x86 platform, the driver checks if the CPU supports AVX512. > - If the CPU supports AVX512 and EAL argument ``--force-max-simd-bitwidth`` > - is set to 512, AVX512 paths will be chosen. > + On the x86 platform, the driver checks if the CPU supports AVX instruction > set. > + If the CPU supports AVX512 and EAL argument --force-max-simd-bitwidth is > set to 512, AVX512 paths will be chosen > + else if --force-max-simd-bitwidth is set to 256, AVX2 paths will be chosen. > > - ``Offload features`` >
Two pieces of feedback here: 1. as stated on patch 2, this doc change should go with the code changes, so merge this patch into previous. 2. For the text itself, please point out that 256 is the default bitwidth in DPDK - just to ensure the user isn't confused that they need to pass extra parameters. Thanks, /Bruce
