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 225707E7B for ; Wed, 22 Oct 2014 16:36:26 +0200 (CEST) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga101.jf.intel.com with ESMTP; 22 Oct 2014 07:44:31 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.04,769,1406617200"; d="scan'208";a="593798667" Received: from pgsmsx101.gar.corp.intel.com ([10.221.44.78]) by orsmga001.jf.intel.com with ESMTP; 22 Oct 2014 07:44:29 -0700 Received: from pgsmsx105.gar.corp.intel.com (10.221.44.96) by PGSMSX101.gar.corp.intel.com (10.221.44.78) with Microsoft SMTP Server (TLS) id 14.3.195.1; Wed, 22 Oct 2014 22:44:07 +0800 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by pgsmsx105.gar.corp.intel.com (10.221.44.96) with Microsoft SMTP Server (TLS) id 14.3.195.1; Wed, 22 Oct 2014 22:44:07 +0800 Received: from shsmsx104.ccr.corp.intel.com ([169.254.5.174]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.44]) with mapi id 14.03.0195.001; Wed, 22 Oct 2014 22:44:07 +0800 From: "Zhou, Danny" To: Thomas Monjalon , "O'driscoll, Tim" Thread-Topic: [dpdk-dev] DPDK Features for Q1 2015 Thread-Index: Ac/tRv4Y4Vfrsm7FTDyvOFKZotGjVAAeVbCAABFi4OA= Date: Wed, 22 Oct 2014 14:44:06 +0000 Message-ID: References: <26FA93C7ED1EAA44AB77D62FBE1D27BA54C361DF@IRSMSX102.ger.corp.intel.com> <1772499.83lI1orZ5e@xps13> In-Reply-To: <1772499.83lI1orZ5e@xps13> 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 14:36:27 -0000 Thomas, In terms of the bifurcated driver, it is actually the same thing. Specifica= lly, the bifurcated=20 driver PMD in DPDK depends on kernel code(af_packet and 10G/40G NIC) change= s. Once the kernel patches are upstreamed, the corresponding DPDK PMDs patches will be= =20 submitted to dpdk.org. John Fastabend and John Ronciak are working with ver= y 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 >=20 > Thanks Tim for sharing your plan. > It's really helpful to improve community collaboration. >=20 > 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. >=20 > I would like to open discussion about a really important feature, > showed last week by John Fastabend and John Ronciak during LinuxCon: >=20 > > Bifurcated Driver: With the Bifurcated Driver, the kernel will retain > > direct control of the NIC, and will assign specific queue pairs to DPDK= . > > Configuration of the NIC is controlled by the kernel via ethtool. >=20 > This design allows to keep the configuration code in one place: the kerne= l. > 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? >=20 > Since you at Intel, you'll be supporting your code, I am fine for duplica= tion, > but I feel it's worth arguing why both should be available instead of one= . >=20 > -- > Thomas