DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: john.mcnamara@intel.com, marko.kovacevic@intel.com,
	shahafs@mellanox.com, yskoh@mellanox.com
Cc: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/3] more doc about isolated mode and bifurcated model
Date: Wed, 30 Jan 2019 12:20:17 +0100	[thread overview]
Message-ID: <20190130112020.871-1-thomas@monjalon.net> (raw)

The flow isolated mode lacks some advertisement in the docs,
especially in association with flow bifurcation.
There was also a miss in flow bifurcation howto for Mellanox case.

Thomas Monjalon (3):
  doc: remove useless anchor for flow API guide
  doc: add references to flow isolated mode in NICs guide
  doc: improve Mellanox bifurcated model description

 doc/guides/howto/flow_bifurcation.rst  | 26 ++++++++++++++++++++++++++
 doc/guides/howto/rte_flow.rst          |  2 +-
 doc/guides/linux_gsg/linux_drivers.rst |  7 ++++++-
 doc/guides/nics/mlx4.rst               |  2 ++
 doc/guides/nics/mlx5.rst               |  2 +-
 doc/guides/nics/mvpp2.rst              |  5 ++++-
 doc/guides/nics/sfc_efx.rst            |  2 ++
 doc/guides/prog_guide/rte_flow.rst     |  8 ++++----
 doc/guides/rel_notes/release_17_02.rst |  3 +--
 9 files changed, 47 insertions(+), 10 deletions(-)

-- 
2.20.1

             reply	other threads:[~2019-01-30 11:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-30 11:20 Thomas Monjalon [this message]
2019-01-30 11:20 ` [dpdk-dev] [PATCH 1/3] doc: remove useless anchor for flow API guide Thomas Monjalon
2019-01-30 11:20 ` [dpdk-dev] [PATCH 2/3] doc: add references to flow isolated mode in NICs guide Thomas Monjalon
2019-01-30 11:20 ` [dpdk-dev] [PATCH 3/3] doc: improve Mellanox bifurcated model description Thomas Monjalon
2019-01-31  6:58 ` [dpdk-dev] [PATCH 0/3] more doc about isolated mode and bifurcated model Shahaf Shuler
2019-01-31 17:36   ` 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=20190130112020.871-1-thomas@monjalon.net \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=shahafs@mellanox.com \
    --cc=yskoh@mellanox.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).