From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id F1F99460FE; Wed, 29 Jan 2025 13:06:01 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 58FDB40609; Wed, 29 Jan 2025 13:05:52 +0100 (CET) Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.13]) by mails.dpdk.org (Postfix) with ESMTP id 939C64026B for ; Wed, 29 Jan 2025 13:05:47 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1738152348; x=1769688348; h=from:to:subject:date:message-id:in-reply-to:references: mime-version:content-transfer-encoding; bh=FnxXb//0F5WAgPgyo8aSeolHmrFxrdv0l4MEsaNTVlw=; b=mFng7NIWw0+LF+SVXLtre0fl4z2ubo0dT0DDDM8mkchi1W4deC/rEYMd AwkMiC49SdBo8NtrusN2Fn1dceav8pdowEzlXOk2uhMiqobmRY6gp2R2G CK793HCCkQ7umXToJDUFIwcO7/T5sNGlGF4QB7nCYtWvxOkDfMZ11akWp RMSuRTEzApkiQxVnQOF8KDmZcmwx7Qt04aFghNxplUESUQyht4kRd22Nw OucEoXX546UHAhN+tVcq+kMrwfyILxuVLLS9qhqMNb15d6l0AEs0tbxl1 EK/Mgx/FbsAgUozjd9S/q/esxsbET/uSSr7Pusb0KlHIWJCDLlz0Hg1BD A==; X-CSE-ConnectionGUID: R4SkuYOvRJ2JLGD5QgPbaA== X-CSE-MsgGUID: uxjL14l/QIG8gcdz8uCRZA== X-IronPort-AV: E=McAfee;i="6700,10204,11329"; a="49644606" X-IronPort-AV: E=Sophos;i="6.13,243,1732608000"; d="scan'208";a="49644606" Received: from fmviesa010.fm.intel.com ([10.60.135.150]) by orvoesa105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Jan 2025 04:05:46 -0800 X-CSE-ConnectionGUID: k6XmZ2CNQmGfYXxyPPozxg== X-CSE-MsgGUID: wgzT5gJ3TO2MDgmqlg79Iw== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.13,243,1732608000"; d="scan'208";a="109567146" Received: from npg-npf-wlpr-srv12.iind.intel.com ([10.190.212.205]) by fmviesa010.fm.intel.com with ESMTP; 29 Jan 2025 04:05:45 -0800 From: Shaiq Wani To: dev@dpdk.org, bruce.richardson@intel.com, aman.deep.singh@intel.com Subject: [PATCH v2 3/3] doc: documentaion update for idpf pmd Date: Wed, 29 Jan 2025 17:48:56 +0530 Message-Id: <20250129121856.1040065-4-shaiq.wani@intel.com> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20250129121856.1040065-1-shaiq.wani@intel.com> References: <20250108121757.170494-2-shaiq.wani@intel.com> <20250129121856.1040065-1-shaiq.wani@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org updated the documentation to reflect that both AVX512 and AVX2 support are available. Signed-off-by: Shaiq Wani --- 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`` -- 2.34.1