> > > > 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? [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 at dpdk.org] On Behalf Of Zhou, Danny > Sent: Wednesday, October 22, 2014 10:44 PM > To: Thomas Monjalon; O'driscoll, Tim > Cc: dev at 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 at dpdk.org] On Behalf Of Thomas Monjalon > > Sent: Wednesday, October 22, 2014 10:21 PM > > To: O'driscoll, Tim > > Cc: dev at 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 at 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 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 available instead of one. > > > > -- > > Thomas
