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 A1790427F2; Tue, 21 Mar 2023 07:34:40 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 2F76840A7F; Tue, 21 Mar 2023 07:34:40 +0100 (CET) Received: from mga06.intel.com (mga06b.intel.com [134.134.136.31]) by mails.dpdk.org (Postfix) with ESMTP id 9FBF240A7A for ; Tue, 21 Mar 2023 07:34:38 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1679380478; x=1710916478; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=z7E/WJiTd5lM2zw0cO+0eXyAYqDmb7vHXNzVAkqU4hg=; b=DH9ktmCetd6uZDDyjU9+53i0Jd3Ygiuqj3jHlRcPa+AWjZ9U4pRqOqwM 1ie2XT78RSb35QcF7wDgODujxsKwoPSfe+hRz+uNogkkDSNp/j09NJYkP NOHi62pUC68mtw99gE+OgBjiCGFUMOFZbC+kyX4GXl4242Fv5oRcTcGDm O3k4trsd/k4jVlH+GdgZSuaqUJX9Ez929E8vMYv2GdZ9X0U+tM/M37yF5 9b6C5XcOKmGF0UZMwRcrpdA4EqGVqqkU7/epkG5tUWfdG3zfcDhuJhVTG X/0U56GIV4c/Tv9TspZ4kxLc+fIfWmwAr3Gmtebjl+ehJqxzYr9+8Ebp+ w==; X-IronPort-AV: E=McAfee;i="6600,9927,10655"; a="401433852" X-IronPort-AV: E=Sophos;i="5.98,278,1673942400"; d="scan'208";a="401433852" Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Mar 2023 23:34:37 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10655"; a="713861610" X-IronPort-AV: E=Sophos;i="5.98,278,1673942400"; d="scan'208";a="713861610" Received: from unknown (HELO localhost.localdomain) ([10.239.252.103]) by orsmga001-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Mar 2023 23:34:35 -0700 From: Zhichao Zeng To: dev@dpdk.org Cc: qi.z.zhang@intel.com, Zhichao Zeng , Jingjing Wu , Beilei Xing Subject: [PATCH] doc: update iavf feature list Date: Tue, 21 Mar 2023 14:39:27 +0800 Message-Id: <20230321063928.785396-1-zhichaox.zeng@intel.com> X-Mailer: git-send-email 2.25.1 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 The iavf supports L3/L4 checksum offload on both scalar and vector path. Signed-off-by: Zhichao Zeng --- doc/guides/nics/features/iavf.ini | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/doc/guides/nics/features/iavf.ini b/doc/guides/nics/features/iavf.ini index 9db2865b71..fbb5b7df32 100644 --- a/doc/guides/nics/features/iavf.ini +++ b/doc/guides/nics/features/iavf.ini @@ -3,6 +3,9 @@ ; ; Refer to default.ini for the full list of available PMD features. ; +; A feature with "P" indicates only be supported when non-vector path +; is selected. +; [Features] Speed capabilities = Y Link status = Y @@ -22,11 +25,11 @@ RSS reta update = Y VLAN filter = Y CRC offload = Y VLAN offload = Y -L3 checksum offload = P -L4 checksum offload = P +L3 checksum offload = Y +L4 checksum offload = Y Timestamp offload = P -Inner L3 checksum = P -Inner L4 checksum = P +Inner L3 checksum = Y +Inner L4 checksum = Y Packet type parsing = Y Rx descriptor status = Y Tx descriptor status = Y -- 2.25.1