From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 3B6615A62 for ; Tue, 4 Aug 2015 19:12:32 +0200 (CEST) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga103.jf.intel.com with ESMTP; 04 Aug 2015 10:12:31 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.15,610,1432623600"; d="scan'208";a="761817126" Received: from irsmsx154.ger.corp.intel.com ([163.33.192.96]) by fmsmga001.fm.intel.com with ESMTP; 04 Aug 2015 10:12:30 -0700 Received: from irsmsx105.ger.corp.intel.com ([169.254.7.223]) by IRSMSX154.ger.corp.intel.com ([169.254.12.253]) with mapi id 14.03.0224.002; Tue, 4 Aug 2015 18:12:29 +0100 From: "Ananyev, Konstantin" To: "Qiu, Michael" , "Zhang, Helin" , Thomas Monjalon , "Liu, Yong" , "Cao, Waterman" Thread-Topic: [dpdk-dev] [RFC] examples: remove l3fwd-vf example Thread-Index: AQHQvkSSYVmvzSC3WkO2UqvxrgDn2J38NEcA Date: Tue, 4 Aug 2015 17:12:29 +0000 Message-ID: <2601191342CEEE43887BDE71AB97725836A6DCA7@irsmsx105.ger.corp.intel.com> References: <1436860647-5862-1-git-send-email-jingjing.wu@intel.com> <2646739.fctqXc0xZm@xps13> <533710CFB86FA344BFBF2D6802E60286046FF05F@SHSMSX101.ccr.corp.intel.com> In-Reply-To: <533710CFB86FA344BFBF2D6802E60286046FF05F@SHSMSX101.ccr.corp.intel.com> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" 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: Tue, 04 Aug 2015 17:12:32 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Qiu, Michael > Sent: Tuesday, August 04, 2015 6:06 PM > To: Zhang, Helin; Thomas Monjalon; Liu, Yong; Cao, Waterman > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] [RFC] examples: remove l3fwd-vf example >=20 > Actually, l3fwd works fine with fm10k vf. >=20 > 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 another > sample with most code are the same compare with l3fwd. Right now, l3fwd is not able to work properly for cases where number of for= warding lcores=20 exceeds number of tx queues on any active port. As an example:=20 2 forwarding lcores and a port with just 1 TX queue (e1000 legacy device). To make l3fwd work for such cases you need to add some sort of synchronisa= tion on TX path. Which means one of 2 ways: either introduce different TX path into l3fwd (one with sync if legacy/vir= ual device is used, another without) and select it on process startup/config phase, or sync overhead for fastpath. Konstantin >=20 > Thanks, > Michael >=20 > On 2015/7/22 7:51, Zhang, Helin wrote: >=20 > Marvin/Waterman >=20 > Could you help to check if l3fwd is good enough for all cases (1g/10/40g,= PF and VF, single queue/multiple queue)? > We aim to remove l3fwd-vf to reduce an example application which is not s= o necessary. > Thank you! >=20 > Regards, > Helin >=20 >=20 >=20 > -----Original Message----- > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] > Sent: Wednesday, July 22, 2015 3:30 AM > To: Zhang, Helin > Cc: dev@dpdk.org; Wu, Jingjing > Subject: Re: [dpdk-dev] [RFC] examples: remove l3fwd-vf example >=20 > 2015-07-14 14:50, Zhang, Helin: >=20 >=20 > From: Wu, Jingjing >=20 >=20 > Because VF multi-queues can be supported, l3fwd can run on vf. > Suggest to remove the l3fwd-vf example. >=20 >=20 > Totally agree with this! > But we need the confirmation from validation guys of that l3fwd works > quite well on VF with all NICs (e.g. i350, 82599, x550, xl710, and fm10k)= . >=20 >=20 >=20 > Helin, any new from validation? >=20 >=20 >=20 >=20