From: "Zhu, Heqing" <heqing.zhu@intel.com> To: "Zhou, Danny" <danny.zhou@intel.com>, "Thomas Monjalon (thomas.monjalon@6wind.com)" <thomas.monjalon@6wind.com>, "O'driscoll, Tim" <tim.o'driscoll@intel.com> Cc: "Fastabend, John R" <john.r.fastabend@intel.com>, "dev@dpdk.org" <dev@dpdk.org>, "Ronciak, John" <john.ronciak@intel.com> Subject: Re: [dpdk-dev] DPDK Features for Q1 2015 Date: Wed, 22 Oct 2014 15:36:11 +0000 Message-ID: <CAD16F236028A64DBBC0158B1636EA4510F8177B@SHSMSX104.ccr.corp.intel.com> (raw) > -----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 > > > > > > > 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, the customer can choose the DPDK with or without the bifurcated driver. > [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 > > > > 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 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
next reply other threads:[~2014-10-22 15:28 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-10-22 15:36 Zhu, Heqing [this message] -- strict thread matches above, loose matches on Subject: below -- 2014-10-22 13:48 [dpdk-dev] [dpdk-announce] " O'driscoll, Tim 2014-10-22 14:20 ` [dpdk-dev] " Thomas Monjalon 2014-10-22 14:44 ` Zhou, Danny 2014-10-22 15:05 ` Liang, Cunming
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=CAD16F236028A64DBBC0158B1636EA4510F8177B@SHSMSX104.ccr.corp.intel.com \ --to=heqing.zhu@intel.com \ --cc=danny.zhou@intel.com \ --cc=dev@dpdk.org \ --cc=john.r.fastabend@intel.com \ --cc=john.ronciak@intel.com \ --cc=thomas.monjalon@6wind.com \ --cc=tim.o'driscoll@intel.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
DPDK patches and discussions This inbox may be cloned and mirrored by anyone: git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \ dev@dpdk.org public-inbox-index dev Example config snippet for mirrors. Newsgroup available over NNTP: nntp://inbox.dpdk.org/inbox.dpdk.dev AGPL code for this site: git clone https://public-inbox.org/public-inbox.git