All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Jingjing Wu <jingjing.wu@intel.com>
Cc: dev@dpdk.org, john.mcnamara@intel.com, yong.liu@intel.com,
	helin.zhang@intel.com
Subject: Re: [PATCH v2 1/2] doc: add bifurcated driver guide on ixgbe nic
Date: Thu, 23 Jun 2016 14:58:53 +0200	[thread overview]
Message-ID: <2397257.zo8BvNnhcC@xps13> (raw)
In-Reply-To: <1466650946-22523-1-git-send-email-jingjing.wu@intel.com>

Hi,

Thank you for providing more doc.
I am just not convinced it is the right place
and it must be discussed.
Some questions below to help deciding where it must be.

2016-06-23 11:02, Jingjing Wu:
> Bifurcated driver is a mechanism which depends the advanced
> Ethernet device to split traffic between queues. It provides
> the capability to let the kernel driver and DPDK driver co-exist
> and take their advantage.

The name "bifurcated driver" was used for a real driver proposal
in Linux. I don't think it applies here.

> It is achieved by using SRIOV and NIC's advanced filtering. This
> patch describes it and adds the user guide on ixgbe NICs.

It is not a DPDK feature, just a use case.
What do we learn about DPDK?

  reply	other threads:[~2016-06-23 12:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-23  3:02 [PATCH v2 1/2] doc: add bifurcated driver guide on ixgbe nic Jingjing Wu
2016-06-23 12:58 ` Thomas Monjalon [this message]
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 ` [PATCH v3] doc: flow bifurcation guide on Linux Jingjing Wu
2016-07-17 19:31   ` Mcnamara, John
2016-07-19  3:31   ` [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

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=2397257.zo8BvNnhcC@xps13 \
    --to=thomas.monjalon@6wind.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.