From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 93AD67E7B for ; Wed, 22 Oct 2014 17:00:58 +0200 (CEST) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga103.fm.intel.com with ESMTP; 22 Oct 2014 08:01:11 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.04,769,1406617200"; d="scan'208";a="609349372" Received: from pgsmsx101.gar.corp.intel.com ([10.221.44.78]) by fmsmga001.fm.intel.com with ESMTP; 22 Oct 2014 08:06:52 -0700 Received: from pgsmsx106.gar.corp.intel.com (10.221.44.98) by PGSMSX101.gar.corp.intel.com (10.221.44.78) with Microsoft SMTP Server (TLS) id 14.3.195.1; Wed, 22 Oct 2014 23:05:34 +0800 Received: from shsmsx103.ccr.corp.intel.com (10.239.4.69) 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:05:34 +0800 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.156]) by SHSMSX103.ccr.corp.intel.com ([169.254.4.207]) with mapi id 14.03.0195.001; Wed, 22 Oct 2014 23:05:33 +0800 From: "Liang, Cunming" To: "Zhou, Danny" , Thomas Monjalon , "O'driscoll, Tim" Thread-Topic: [dpdk-dev] DPDK Features for Q1 2015 Thread-Index: Ac/tRv4Y4Vfrsm7FTDyvOFKZotGjVAAeVbCAABFi4OAAAIKSkA== Date: Wed, 22 Oct 2014 15:05:32 +0000 Message-ID: References: <26FA93C7ED1EAA44AB77D62FBE1D27BA54C361DF@IRSMSX102.ger.corp.intel.com> <1772499.83lI1orZ5e@xps13> In-Reply-To: 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: "dev@dpdk.org" , "Fastabend, John R" , "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:00:59 -0000 > > > > This design allows to keep the configuration code in one place: the ker= nel. > > In the meantime, we are trying to add a lot of code to configure the NI= Cs, > > which looks to be a duplication of effort. > > Why should we have two ways of configuring e.g. flow director? [Liang, Cunming] The HW sometimes provides additional ability than existing= abstraction API. On that time(HW ability is a superset to the abstraction wrapper, e.g. flow= 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. > -----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 >=20 > Thomas, >=20 > In terms of the bifurcated driver, it is actually the same thing. Specifi= cally, 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 b= e > submitted to dpdk.org. John Fastabend and John Ronciak are working with v= ery > closely to achieve the same goal. >=20 > -Danny >=20 > > -----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 pairs to DP= DK. > > > Configuration of the NIC is controlled by the kernel via ethtool. > > > > This design allows to keep the configuration code in one place: the ker= nel. > > In the meantime, we are trying to add a lot of code to configure the NI= Cs, > > 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 dupli= cation, > > but I feel it's worth arguing why both should be available instead of o= ne. > > > > -- > > Thomas