DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Wu, Jingjing" <jingjing.wu@intel.com>
Cc: dev@dpdk.org, "Mcnamara, John" <john.mcnamara@intel.com>,
	"Liu, Yong" <yong.liu@intel.com>,
	"Zhang, Helin" <helin.zhang@intel.com>,
	"Iremonger, Bernard" <bernard.iremonger@intel.com>
Subject: Re: [dpdk-dev] [PATCH v4] doc: flow bifurcation guide on Linux
Date: Fri, 22 Jul 2016 10:23:00 -0700 (PDT)	[thread overview]
Message-ID: <1564213.HiMhRdu1Yu@xps13> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE2025A3363@IRSMSX103.ger.corp.intel.com>

> > Flow Bifurcation is a mechanism which uses features of advanced Ethernet
> > devices to split traffic between queues. It provides the capability to let
> > the kernel driver and DPDK driver co-exist and take advantage of both.
> > 
> > It is achieved by using SR-IOV and the NIC's advanced filtering. This
> > patch describes Flow Bifurcation and adds the user guide for ixgbe and
> > i40e NICs.
> > 
> > Signed-off-by: Jingjing Wu <jingjing.wu@intel.com>
> 
> Acked-by: John McNamara <john.mcnamara@intel.com>

Applied, thanks

      parent reply	other threads:[~2016-07-22 17:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-23  3:02 [dpdk-dev] [PATCH v2 1/2] doc: add bifurcated driver guide on ixgbe nic Jingjing Wu
2016-06-23 12:58 ` Thomas Monjalon
2016-07-08  8:42   ` Wu, Jingjing
2016-07-08  9:14     ` Thomas Monjalon
2016-07-08  9:24       ` Mcnamara, John
2016-07-11  5:50       ` Wu, Jingjing
2016-07-14  8:04 ` [dpdk-dev] [PATCH v3] doc: flow bifurcation guide on Linux Jingjing Wu
2016-07-17 19:31   ` Mcnamara, John
2016-07-19  3:31   ` [dpdk-dev] [PATCH v4] " Jingjing Wu
2016-07-19 16:34     ` Mcnamara, John
2016-07-20  0:59       ` Wu, Jingjing
2016-07-22 17:23       ` Thomas Monjalon [this message]

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=1564213.HiMhRdu1Yu@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=bernard.iremonger@intel.com \
    --cc=dev@dpdk.org \
    --cc=helin.zhang@intel.com \
    --cc=jingjing.wu@intel.com \
    --cc=john.mcnamara@intel.com \
    --cc=yong.liu@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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).