From patchwork Thu Aug 17 09:08:12 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: "Hu, Jiayu" X-Patchwork-Id: 27627 Return-Path: X-Original-To: patchwork@dpdk.org Delivered-To: patchwork@dpdk.org Received: from [92.243.14.124] (localhost [IPv6:::1]) by dpdk.org (Postfix) with ESMTP id 80F7A9970; Thu, 17 Aug 2017 11:06:12 +0200 (CEST) Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 6AE5B9965 for ; Thu, 17 Aug 2017 11:06:09 +0200 (CEST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 Aug 2017 02:06:09 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.41,387,1498546800"; d="scan'208";a="124663432" Received: from dpdk15.sh.intel.com ([10.67.111.77]) by orsmga002.jf.intel.com with ESMTP; 17 Aug 2017 02:06:06 -0700 From: Jiayu Hu To: dev@dpdk.org Cc: ferruh.yigit@intel.com, konstantin.ananyev@intel.com, jianfeng.tan@intel.com, thomas@monjalon.net, jingjing.wu@intel.com, lei.a.yao@intel.com, Jiayu Hu Date: Thu, 17 Aug 2017 17:08:12 +0800 Message-Id: <1502960892-112960-3-git-send-email-jiayu.hu@intel.com> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1502960892-112960-1-git-send-email-jiayu.hu@intel.com> References: <1502333448-75976-1-git-send-email-jiayu.hu@intel.com> <1502960892-112960-1-git-send-email-jiayu.hu@intel.com> Subject: [dpdk-dev] [PATCH v2 2/2] doc: update testpmd user guide for the heavyweight mode GRO X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" This patch is to update testpmd user guide for the heavyweight mode GRO. Signed-off-by: Jiayu Hu --- doc/guides/testpmd_app_ug/testpmd_funcs.rst | 37 +++++++++++++++++++++++------ 1 file changed, 30 insertions(+), 7 deletions(-) diff --git a/doc/guides/testpmd_app_ug/testpmd_funcs.rst b/doc/guides/testpmd_app_ug/testpmd_funcs.rst index 2ed62f5..fa507ef 100644 --- a/doc/guides/testpmd_app_ug/testpmd_funcs.rst +++ b/doc/guides/testpmd_app_ug/testpmd_funcs.rst @@ -898,12 +898,12 @@ Display the status of TCP Segmentation Offload:: testpmd> tso show (port_id) -gro -~~~ +set port - gro +~~~~~~~~~~~~~~ Enable or disable GRO in ``csum`` forwarding engine:: - testpmd> gro (on|off) (port_id) + testpmd> set port (port_id) gro (heavymode|lightmode) (on|off) If enabled, the csum forwarding engine will perform GRO on the TCP/IPv4 packets received from the given port. @@ -914,10 +914,18 @@ GRO. By default, GRO is disabled for all ports. .. note:: When enable GRO for a port, TCP/IPv4 packets received from the port - will be performed GRO. After GRO, the merged packets are multi-segments. - But csum forwarding engine doesn't support to calculate TCP checksum - for multi-segment packets in SW. So please select TCP HW checksum - calculation for the port which GROed packets are transmitted to. + will be performed GRO. After GRO, all merged packets have bad + checksums, since the GRO library doesn't re-calculate checksums for + the merged packets. Therefore, if users want the merged packets to + have correct checksums, please select IP and TCP HW checksum calculation + for the port which the merged packets are transmitted to. + +show port - gro +~~~~~~~~~~~~~~~ + +Display GRO configuration:: + + testpmd> show port (port_id) gro gro set ~~~~~~~ @@ -932,6 +940,21 @@ number of packets a GRO table can store. If current packet number is greater than or equal to the max value, GRO will stop processing incoming packets. +set gro flush interval +~~~~~~~~~~~~~~~~~~~~~~ + +Set the interval of flushing GROed packets from reassembly tables:: + + testpmd> set gro flush interval (num) + +In the heavyweight mode, GROed packets are stored in reassembly tables +and need flushing from the tables manually. This command is to set the +number of performing GRO operations between two flushing operations. + +The value of ``num`` should be in the range of 0 to ``GRO_MAX_FLUSH_INTERVAL``. +``0`` means flush GROed packets from the tables when one GRO operation +finishes. + mac_addr add ~~~~~~~~~~~~