From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from new3-smtp.messagingengine.com (new3-smtp.messagingengine.com [66.111.4.229]) by dpdk.org (Postfix) with ESMTP id 3EE2D1B435 for ; Mon, 22 Apr 2019 21:49:32 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailnew.nyi.internal (Postfix) with ESMTP id C5F96128D9; Mon, 22 Apr 2019 15:49:31 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Mon, 22 Apr 2019 15:49:31 -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=gUOT0b9w5UE6oK9GRb3Zot7UunETKITK9tjjnrkdTKU=; b=UfojyyjfpP3C 9ZzyGTheCPSMnjyKNCPPGZBE8GhHiNBnOoRBBgc2OxadD60iLiq/44VrdxT4gd5d gUsinRODlu0AAsQHPRScIAnLGCC6H6NhsqIPsxDIL3ZZVHXNLWrZ5MMx8XjgW7xM Rur6KmjkbX1UWPg1IO2l/rmg7O7IqsM= 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=gUOT0b9w5UE6oK9GRb3Zot7UunETKITK9tjjnrkdT KU=; b=NCz5cckXM17wfc6560f0I02a0CPHgRjn6H9nRFpyGEnvhfRtFLvimwAru ZIoq9RClA0DpZSMdoshjVA7tGg6NWAiG9fcYXrIGRwVHDa1E3PbBmp353GVyMDPF d2XXqeyLIm/U3j2gEcYc5kxLS0F0hq5g3Ev7PKhWXDzeyMbjf490881JTGQyK6GF agBW8RHOYn88EanOWbdqojOA9z35M3n1SLq2Itv8eXT2to7vzVDzco9MJeVarVcA mNp0Rt2o2JPLZCrrxfSjoQ/UOGFhsOFGj/89UnRdZflBHWKZkJx5rf1gFC2L7AAX e9PIay50JigCLJ8F2BEA9vXaVMG+w== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrgeeigddufeeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukf hppeekfedrudduhedrudehhedrudefkeenucfrrghrrghmpehmrghilhhfrhhomhepthhh ohhmrghssehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from xps.localnet (acaen-257-1-30-138.w83-115.abo.wanadoo.fr [83.115.155.138]) by mail.messagingengine.com (Postfix) with ESMTPA id 27724103C9; Mon, 22 Apr 2019 15:49:27 -0400 (EDT) From: Thomas Monjalon To: Vipin Varghese Cc: dev@dpdk.org, marko.kovacevic@intel.com, reshma.pattan@intel.com, david.marchand@redhat.com, keith.wiles@intel.com, john.mcnamara@intel.com, stephen1.byrne@intel.com, amit.tamboli@intel.com, sanjay.padubidri@intel.com, amol.patel@intel.com Date: Mon, 22 Apr 2019 21:49:24 +0200 Message-ID: <4397496.6pO4jSxo1K@xps> In-Reply-To: <20190404085515.15789-1-vipin.varghese@intel.com> References: <20190402091836.35779-3-vipin.varghese@intel.com> <20190404085515.15789-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 v6 0/2] app/pdump: enhance to support unique cores 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: Mon, 22 Apr 2019 19:49:32 -0000 04/04/2019 10:55, Vipin Varghese: > The patch series enhances application to support pdump capture to run > on unique cores. > > Motivation > ========== > > DPDK pdump capture tool currently runs as secondary on the default core 0. > For all --pdump, core 0 iterates and capture packets. This leads to drops > and delay in the capture. This introduces skew in result and performance > bottleneck. > > In order to allow --pdump to unique cores, the pdump application has to be > support multi-core in EAL arguments and each --pdump has to be mapped to > unique cores. 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 8DBCFA05D3 for ; Mon, 22 Apr 2019 21:49:34 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 4FB691B453; Mon, 22 Apr 2019 21:49:33 +0200 (CEST) Received: from new3-smtp.messagingengine.com (new3-smtp.messagingengine.com [66.111.4.229]) by dpdk.org (Postfix) with ESMTP id 3EE2D1B435 for ; Mon, 22 Apr 2019 21:49:32 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailnew.nyi.internal (Postfix) with ESMTP id C5F96128D9; Mon, 22 Apr 2019 15:49:31 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Mon, 22 Apr 2019 15:49:31 -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=gUOT0b9w5UE6oK9GRb3Zot7UunETKITK9tjjnrkdTKU=; b=UfojyyjfpP3C 9ZzyGTheCPSMnjyKNCPPGZBE8GhHiNBnOoRBBgc2OxadD60iLiq/44VrdxT4gd5d gUsinRODlu0AAsQHPRScIAnLGCC6H6NhsqIPsxDIL3ZZVHXNLWrZ5MMx8XjgW7xM Rur6KmjkbX1UWPg1IO2l/rmg7O7IqsM= 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=gUOT0b9w5UE6oK9GRb3Zot7UunETKITK9tjjnrkdT KU=; b=NCz5cckXM17wfc6560f0I02a0CPHgRjn6H9nRFpyGEnvhfRtFLvimwAru ZIoq9RClA0DpZSMdoshjVA7tGg6NWAiG9fcYXrIGRwVHDa1E3PbBmp353GVyMDPF d2XXqeyLIm/U3j2gEcYc5kxLS0F0hq5g3Ev7PKhWXDzeyMbjf490881JTGQyK6GF agBW8RHOYn88EanOWbdqojOA9z35M3n1SLq2Itv8eXT2to7vzVDzco9MJeVarVcA mNp0Rt2o2JPLZCrrxfSjoQ/UOGFhsOFGj/89UnRdZflBHWKZkJx5rf1gFC2L7AAX e9PIay50JigCLJ8F2BEA9vXaVMG+w== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrgeeigddufeeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukf hppeekfedrudduhedrudehhedrudefkeenucfrrghrrghmpehmrghilhhfrhhomhepthhh ohhmrghssehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from xps.localnet (acaen-257-1-30-138.w83-115.abo.wanadoo.fr [83.115.155.138]) by mail.messagingengine.com (Postfix) with ESMTPA id 27724103C9; Mon, 22 Apr 2019 15:49:27 -0400 (EDT) From: Thomas Monjalon To: Vipin Varghese Cc: dev@dpdk.org, marko.kovacevic@intel.com, reshma.pattan@intel.com, david.marchand@redhat.com, keith.wiles@intel.com, john.mcnamara@intel.com, stephen1.byrne@intel.com, amit.tamboli@intel.com, sanjay.padubidri@intel.com, amol.patel@intel.com Date: Mon, 22 Apr 2019 21:49:24 +0200 Message-ID: <4397496.6pO4jSxo1K@xps> In-Reply-To: <20190404085515.15789-1-vipin.varghese@intel.com> References: <20190402091836.35779-3-vipin.varghese@intel.com> <20190404085515.15789-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 v6 0/2] app/pdump: enhance to support unique cores 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: <20190422194924.i9ZZmikkLCKePu5EFiy_1akHic-lAcZlp7npCVL_RRg@z> 04/04/2019 10:55, Vipin Varghese: > The patch series enhances application to support pdump capture to run > on unique cores. > > Motivation > ========== > > DPDK pdump capture tool currently runs as secondary on the default core 0. > For all --pdump, core 0 iterates and capture packets. This leads to drops > and delay in the capture. This introduces skew in result and performance > bottleneck. > > In order to allow --pdump to unique cores, the pdump application has to be > support multi-core in EAL arguments and each --pdump has to be mapped to > unique cores. Applied, thanks