From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 07BEE2BF8 for ; Wed, 20 Apr 2016 13:16:56 +0200 (CEST) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga104.fm.intel.com with ESMTP; 20 Apr 2016 04:16:55 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,509,1455004800"; d="scan'208";a="949090169" Received: from irsmsx153.ger.corp.intel.com ([163.33.192.75]) by fmsmga001.fm.intel.com with ESMTP; 20 Apr 2016 04:16:54 -0700 Received: from irsmsx105.ger.corp.intel.com ([169.254.7.35]) by IRSMSX153.ger.corp.intel.com ([169.254.9.178]) with mapi id 14.03.0248.002; Wed, 20 Apr 2016 12:16:53 +0100 From: "Ananyev, Konstantin" To: Thomas Monjalon CC: "Qiu, Michael" , "Zhang, Helin" , "Liu, Yong" , "Cao, Waterman" , "dev@dpdk.org" Thread-Topic: [dpdk-dev] [RFC] examples: remove l3fwd-vf example Thread-Index: AQHRmvH5fDEkTvwn9UWWcWvgXd7OwJ+StVpg Date: Wed, 20 Apr 2016 11:16:53 +0000 Message-ID: <2601191342CEEE43887BDE71AB97725836B3FEA2@irsmsx105.ger.corp.intel.com> References: <1436860647-5862-1-git-send-email-jingjing.wu@intel.com> <533710CFB86FA344BFBF2D6802E60286046FF05F@SHSMSX101.ccr.corp.intel.com> <2601191342CEEE43887BDE71AB97725836A6DCA7@irsmsx105.ger.corp.intel.com> <4008817.HUC273QNcu@xps13> In-Reply-To: <4008817.HUC273QNcu@xps13> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNWNiNjFlYzYtOTMyZS00MTIzLThkNDctOTk2YjQyNDFkNmZmIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IjdHcXRvK1ZEZHBxYU0reGgrbGVSZjdLZ0tmVUtBd1FuNUxWZ1VpeG1YQlE9In0= x-ctpclassification: CTP_IC x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [RFC] examples: remove l3fwd-vf example 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: Wed, 20 Apr 2016 11:16:57 -0000 Hi Thomas, > -----Original Message----- > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] > Sent: Wednesday, April 20, 2016 11:47 AM > To: Ananyev, Konstantin > Cc: Qiu, Michael; Zhang, Helin; Liu, Yong; Cao, Waterman; dev@dpdk.org > Subject: Re: [dpdk-dev] [RFC] examples: remove l3fwd-vf example >=20 > 2015-08-04 17:12, Ananyev, Konstantin: > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Qiu, Michael > > > Actually, l3fwd works fine with fm10k vf. > > > > > > I don't know what's the exact reason of l3fwd-vf still in DPDK, > > > at least we could make full support for vf in l3fwd instead of anothe= r > > > sample with most code are the same compare with l3fwd. > > > > Right now, l3fwd is not able to work properly for cases where number of= forwarding lcores > > exceeds number of tx queues on any active port. > > As an example: > > 2 forwarding lcores and a port with just 1 TX queue (e1000 legacy devic= e). > > > > To make l3fwd work for such cases you need to add some sort of synchro= nisation on TX path. > > Which means one of 2 ways: > > either introduce different TX path into l3fwd (one with sync if legacy= /virual device is used, another without) > > and select it on process startup/config phase, > > or sync overhead for fastpath. >=20 > Any news about removing l3fwd-vf example? >=20 > l3fwd has been reworked but l3fwd-power, l3fwd-vf and l3fwd-thread are > still based on the old l3fwd with APP_LOOKUP_METHOD compile-time flag. As far as I know, no-one from Intel side is working on it right now. Konstantin =20