From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id D9B4CA3 for ; Sun, 5 May 2019 00:26:38 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 6E52721B24; Sat, 4 May 2019 18:26:38 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Sat, 04 May 2019 18:26:38 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=hDbi0neJuS5AaeKl8d7F5REzzzxzN2h7Q+MTm3hE//Q=; b=OJqDrG1gDFPR CHTQ4WaruxdtX2+eWKbRC+/oxiF6+awtB0yHhBNHmfUNxkR8o7Gd/9nRZX1fAlGF eTVG3OYuEL7iNb81YQheSIkFd+03JIKZYLZIYjhmW6KpcjmVFy9d/I7iynlIiB5N BLqgYJqgGtxAjrBERbETGMkIqvAE41Q= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=hDbi0neJuS5AaeKl8d7F5REzzzxzN2h7Q+MTm3hE/ /Q=; b=CuRH0rVHU/HSNbrB3UojYAPSe2DT/6sSynw+4M3D1jQD1f7TKEqxgkOts kqVjAmScVuYNg+hb4jtJ2zPLxp/AkzFUdzjyoT1y1rixI/MvmbRVyEfVljMfjqwg aImC3aUbBd6Ct4V9xxE2hNwpjLRvhT4Qvm+3g4ftxCX+lfU6Pr9voB0Mmtbym6e4 82W+cV4qPG7ZKoPOeBtddTb7d3iaj1Qob0Dhbl9hGyr7j5IP/VAGHiV++diLFN+Z +kSaEYwyskEFF1LCTpGlfkr0cetl2hJhx2Yz3i2CgB8UyLcAiqbzMbghZTO0r0cs 5MgD/CUwdWophpZKr5mJEgkGlTyUg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrjeeggdduudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkph epjeejrddufeegrddvtdefrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhho mhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 77E45E432B; Sat, 4 May 2019 18:26:36 -0400 (EDT) From: Thomas Monjalon To: Vipin Varghese Cc: dev@dpdk.org, marko.kovacevic@intel.com, john.mcnamara@intel.com, shreyansh.jain@nxp.com, keith.wiles@intel.com, amit.tamboli@intel.com, sanjay.padubidri@intel.com, amol.patel@intel.com, ferruh.yigit@intel.com Date: Sun, 05 May 2019 00:26:35 +0200 Message-ID: <4460290.4R7cWu72cf@xps> In-Reply-To: <20190409063344.36564-1-vipin.varghese@intel.com> References: <20190225171222.64134-3-vipin.varghese@intel.com> <20190409063344.36564-1-vipin.varghese@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v8 0/2] guide to debug and troubleshoot. 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: , X-List-Received-Date: Sat, 04 May 2019 22:26:39 -0000 09/04/2019 08:33, Vipin Varghese: > The patch series adds a how-to guide for debugging and > troubleshooting tips. > > Motivation > ========== > > DPDK proc-info tool is been enhanced to accommodate the debug information > for the port, traffic manager crypto, ring and mempool contents. With these > additional information, it becomes easy to analyze issues and performance > variance. > > But applications are designed based on the target platform, workload, poll > mode drivers, and multi-process. This raises variance in debugging and > collecting data. Hence attempt of patch series is identified such symptoms > and share step by step guide to cover the cases. > > Not all possible cases could be covered in a single attempt. But with > feedback and support from the community, this can be expanded. I removed _guide at the end of the filename, and applied, thanks. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 8F96AA0AC5 for ; Sun, 5 May 2019 00:26:41 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 258BB1041; Sun, 5 May 2019 00:26:40 +0200 (CEST) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id D9B4CA3 for ; Sun, 5 May 2019 00:26:38 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 6E52721B24; Sat, 4 May 2019 18:26:38 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Sat, 04 May 2019 18:26:38 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=hDbi0neJuS5AaeKl8d7F5REzzzxzN2h7Q+MTm3hE//Q=; b=OJqDrG1gDFPR CHTQ4WaruxdtX2+eWKbRC+/oxiF6+awtB0yHhBNHmfUNxkR8o7Gd/9nRZX1fAlGF eTVG3OYuEL7iNb81YQheSIkFd+03JIKZYLZIYjhmW6KpcjmVFy9d/I7iynlIiB5N BLqgYJqgGtxAjrBERbETGMkIqvAE41Q= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=hDbi0neJuS5AaeKl8d7F5REzzzxzN2h7Q+MTm3hE/ /Q=; b=CuRH0rVHU/HSNbrB3UojYAPSe2DT/6sSynw+4M3D1jQD1f7TKEqxgkOts kqVjAmScVuYNg+hb4jtJ2zPLxp/AkzFUdzjyoT1y1rixI/MvmbRVyEfVljMfjqwg aImC3aUbBd6Ct4V9xxE2hNwpjLRvhT4Qvm+3g4ftxCX+lfU6Pr9voB0Mmtbym6e4 82W+cV4qPG7ZKoPOeBtddTb7d3iaj1Qob0Dhbl9hGyr7j5IP/VAGHiV++diLFN+Z +kSaEYwyskEFF1LCTpGlfkr0cetl2hJhx2Yz3i2CgB8UyLcAiqbzMbghZTO0r0cs 5MgD/CUwdWophpZKr5mJEgkGlTyUg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrjeeggdduudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucfkph epjeejrddufeegrddvtdefrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhho mhgrshesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 77E45E432B; Sat, 4 May 2019 18:26:36 -0400 (EDT) From: Thomas Monjalon To: Vipin Varghese Cc: dev@dpdk.org, marko.kovacevic@intel.com, john.mcnamara@intel.com, shreyansh.jain@nxp.com, keith.wiles@intel.com, amit.tamboli@intel.com, sanjay.padubidri@intel.com, amol.patel@intel.com, ferruh.yigit@intel.com Date: Sun, 05 May 2019 00:26:35 +0200 Message-ID: <4460290.4R7cWu72cf@xps> In-Reply-To: <20190409063344.36564-1-vipin.varghese@intel.com> References: <20190225171222.64134-3-vipin.varghese@intel.com> <20190409063344.36564-1-vipin.varghese@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [PATCH v8 0/2] guide to debug and troubleshoot. 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" Message-ID: <20190504222635.eZpf8mBMxmVLcrQiUkPmUu1RJA7SFx_nHMBnbw6F1gQ@z> 09/04/2019 08:33, Vipin Varghese: > The patch series adds a how-to guide for debugging and > troubleshooting tips. > > Motivation > ========== > > DPDK proc-info tool is been enhanced to accommodate the debug information > for the port, traffic manager crypto, ring and mempool contents. With these > additional information, it becomes easy to analyze issues and performance > variance. > > But applications are designed based on the target platform, workload, poll > mode drivers, and multi-process. This raises variance in debugging and > collecting data. Hence attempt of patch series is identified such symptoms > and share step by step guide to cover the cases. > > Not all possible cases could be covered in a single attempt. But with > feedback and support from the community, this can be expanded. I removed _guide at the end of the filename, and applied, thanks.