All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
	"Wu, Jingjing" <jingjing.wu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Liu, Yong" <yong.liu@intel.com>,
	"Zhang, Helin" <helin.zhang@intel.com>,
	"Iremonger, Bernard" <bernard.iremonger@intel.com>
Subject: Re: [PATCH v2 1/2] doc: add bifurcated driver guide on ixgbe nic
Date: Fri, 8 Jul 2016 09:24:20 +0000	[thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE20258D176@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <367000689.y0psKNqMLI@xps13>

> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Friday, July 8, 2016 10:14 AM
> 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 v2 1/2] doc: add bifurcated driver guide on
> ixgbe nic
> 
> >
> > Yes, it is an feature in Linux driver. And the typical use case how DPDK
> co-work with Linux networking.
> > I think it will be a good reference. When I preparde this patch, I'm
> > also doubt where to put, and the behavior may be NIC specific, so I
> added it here.
> >
> > Any other suggestion?
> 
> Bernard is creating an howto section.


I think a howto section would be good for this too.

John

  reply	other threads:[~2016-07-08  9:24 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
2016-07-08  8:42   ` Wu, Jingjing
2016-07-08  9:14     ` Thomas Monjalon
2016-07-08  9:24       ` Mcnamara, John [this message]
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=B27915DBBA3421428155699D51E4CFE20258D176@IRSMSX103.ger.corp.intel.com \
    --to=john.mcnamara@intel.com \
    --cc=bernard.iremonger@intel.com \
    --cc=dev@dpdk.org \
    --cc=helin.zhang@intel.com \
    --cc=jingjing.wu@intel.com \
    --cc=thomas.monjalon@6wind.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.