From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id DD8639E7 for ; Thu, 21 Apr 2016 13:00:22 +0200 (CEST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga101.fm.intel.com with ESMTP; 21 Apr 2016 04:00:22 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,512,1455004800"; d="scan'208";a="959726891" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.220.132]) by orsmga002.jf.intel.com with SMTP; 21 Apr 2016 04:00:19 -0700 Received: by (sSMTP sendmail emulation); Thu, 21 Apr 2016 12:00:18 +0025 Date: Thu, 21 Apr 2016 12:00:18 +0100 From: Bruce Richardson To: Thomas Monjalon Cc: Zhihong Wang , dev@dpdk.org, Pablo de Lara Message-ID: <20160421110018.GB11224@bricha3-MOBL3> References: <1461192195-104070-1-git-send-email-zhihong.wang@intel.com> <1946900.ocWSxO32dE@xps13> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1946900.ocWSxO32dE@xps13> Organization: Intel Shannon Ltd. User-Agent: Mutt/1.5.23 (2014-03-12) Subject: Re: [dpdk-dev] [RFC PATCH 0/2] performance utility in testpmd X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2016 11:00:23 -0000 On Thu, Apr 21, 2016 at 11:54:12AM +0200, Thomas Monjalon wrote: > 2016-04-20 18:43, Zhihong Wang: > > This RFC patch proposes a general purpose forwarding engine in testpmd > > namely "portfwd", to enable performance analysis and tuning for poll mode > > drivers in vSwitching scenarios. > > > > > > Problem statement > > ----------------- > > > > vSwitching is more I/O bound in a lot of cases since there are a lot of > > LLC/cross-core memory accesses. > > > > In order to reveal memory/cache behavior in real usage scenarios and enable > > efficient performance analysis and tuning for vSwitching, DPDK needs a > > sample application that supports traffic flow close to real deployment, > > e.g. multi-tenancy, service chaining. > > > > There is a vhost sample application currently to enable simple vSwitching > > scenarios, it comes with several limitations: > > > > 1) Traffic flow is too simple and not flexible > > > > 2) Switching based on MAC/VLAN only > > > > 3) Not enough performance metrics > > > > > > Proposed solution > > ----------------- > > > > The testpmd sample application is a good choice, it's a powerful poll mode > > driver management framework hosts various forwarding engine. > > Not sure it is a good choice. > The goal of testpmd is to test every PMD features. > How far can we go in adding some stack processing while keeping it > easily maintainable? I was thinking the exact same thing. Would it not be better to enhance the existing vhost example application to remove the limitations you call out above? I don't particularly like the idea of introducing protocol awareness into testpmd for IP forwarding, for instance. Regards, /Bruce