From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id C4E597E7B for ; Wed, 22 Oct 2014 17:28:27 +0200 (CEST) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga101.jf.intel.com with ESMTP; 22 Oct 2014 08:36:47 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.04,769,1406617200"; d="scan'208";a="593834899" Received: from pgsmsx103.gar.corp.intel.com ([10.221.44.82]) by orsmga001.jf.intel.com with ESMTP; 22 Oct 2014 08:36:14 -0700 Received: from pgsmsx106.gar.corp.intel.com (10.221.44.98) by PGSMSX103.gar.corp.intel.com (10.221.44.82) with Microsoft SMTP Server (TLS) id 14.3.195.1; Wed, 22 Oct 2014 23:36:13 +0800 Received: from shsmsx102.ccr.corp.intel.com (10.239.4.154) by pgsmsx106.gar.corp.intel.com (10.221.44.98) with Microsoft SMTP Server (TLS) id 14.3.195.1; Wed, 22 Oct 2014 23:36:13 +0800 Received: from shsmsx104.ccr.corp.intel.com ([169.254.5.174]) by shsmsx102.ccr.corp.intel.com ([169.254.2.156]) with mapi id 14.03.0195.001; Wed, 22 Oct 2014 23:36:11 +0800 From: "Zhu, Heqing" To: "Zhou, Danny" , "Thomas Monjalon (thomas.monjalon@6wind.com)" , "O'driscoll, Tim" Thread-Topic: [dpdk-dev] DPDK Features for Q1 2015 Thread-Index: Ac/uDeVmoSG/ryizS2iGSL3D4ChrTQ== Date: Wed, 22 Oct 2014 15:36:11 +0000 Message-ID: Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "Fastabend, John R" , "dev@dpdk.org" , "Ronciak, John" Subject: Re: [dpdk-dev] DPDK Features for Q1 2015 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, 22 Oct 2014 15:28:28 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Liang, Cunming > Sent: Wednesday, October 22, 2014 8:06 AM > To: Zhou, Danny; Thomas Monjalon; O'driscoll, Tim > Cc: dev@dpdk.org; Fastabend, John R; Ronciak, John > Subject: Re: [dpdk-dev] DPDK Features for Q1 2015 >=20 > > > > > > This design allows to keep the configuration code in one place: the > kernel. > > > In the meantime, we are trying to add a lot of code to configure the > > > NICs, which looks to be a duplication of effort. > > > Why should we have two ways of configuring e.g. flow director? [heqing] There will be multiple choices for DPDK usage model if/after this = feature is available,=20 the customer can choose the DPDK with or without the bifurcated driver.=20 > [Liang, Cunming] The HW sometimes provides additional ability than existi= ng > abstraction API. > On that time(HW ability is a superset to the abstraction wrapper, e.g. fl= ow > director), we need to provide another choice. > Ethtools is good, but can't apply anything supported in NIC. > Bifurcated driver considers a lot on reusing existing rx/tx routine. > We'll send RFC patch soon if kernel patch moving fast. >=20 > > -----Original Message----- > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Zhou, Danny > > Sent: Wednesday, October 22, 2014 10:44 PM > > To: Thomas Monjalon; O'driscoll, Tim > > Cc: dev@dpdk.org; Fastabend, John R; Ronciak, John > > Subject: Re: [dpdk-dev] DPDK Features for Q1 2015 > > > > Thomas, > > > > In terms of the bifurcated driver, it is actually the same thing. > > Specifically, the bifurcated driver PMD in DPDK depends on kernel > > code(af_packet and 10G/40G NIC) changes. Once the kernel patches are > > upstreamed, the corresponding DPDK PMDs patches will be submitted to > > dpdk.org. John Fastabend and John Ronciak are working with very > > closely to achieve the same goal. > > > > -Danny > > > > > -----Original Message----- > > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas > Monjalon > > > Sent: Wednesday, October 22, 2014 10:21 PM > > > To: O'driscoll, Tim > > > Cc: dev@dpdk.org; Fastabend, John R; Ronciak, John > > > Subject: Re: [dpdk-dev] DPDK Features for Q1 2015 > > > > > > Thanks Tim for sharing your plan. > > > It's really helpful to improve community collaboration. > > > > > > I'm sure it's going to generate some interesting discussions. > > > Please take care to discuss such announce on dev list only. > > > The announce@dpdk.org list is moderated to keep a low traffic. > > > > > > I would like to open discussion about a really important feature, > > > showed last week by John Fastabend and John Ronciak during LinuxCon: > > > > > > > Bifurcated Driver: With the Bifurcated Driver, the kernel will > > > > retain direct control of the NIC, and will assign specific queue pa= irs to > DPDK. > > > > Configuration of the NIC is controlled by the kernel via ethtool. > > > > > > This design allows to keep the configuration code in one place: the > kernel. > > > In the meantime, we are trying to add a lot of code to configure the > > > NICs, which looks to be a duplication of effort. > > > Why should we have two ways of configuring e.g. flow director? > > > > > > Since you at Intel, you'll be supporting your code, I am fine for > > > duplication, but I feel it's worth arguing why both should be availab= le > instead of one. > > > > > > -- > > > Thomas