From: Thomas Monjalon <thomas@monjalon.net>
To: Shahaf Shuler <shahafs@mellanox.com>
Cc: dev@dpdk.org, "john.mcnamara@intel.com" <john.mcnamara@intel.com>,
"marko.kovacevic@intel.com" <marko.kovacevic@intel.com>,
Yongseok Koh <yskoh@mellanox.com>
Subject: Re: [PATCH 0/3] more doc about isolated mode and bifurcated model
Date: Thu, 31 Jan 2019 18:36:56 +0100 [thread overview]
Message-ID: <1918029.g09UHAWXCS@xps> (raw)
In-Reply-To: <AM6PR0502MB3797070919451B6A7B03DC28C3910@AM6PR0502MB3797.eurprd05.prod.outlook.com>
31/01/2019 07:58, Shahaf Shuler:
> Wednesday, January 30, 2019 1:20 PM, Thomas Monjalon:
> > Subject: [dpdk-dev] [PATCH 0/3] more doc about isolated mode and
> > bifurcated model
> >
> > 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
>
> For the series - Acked-by: Shahaf Shuler <shahafs@mellanox.com>
Applied
prev parent reply other threads:[~2019-01-31 17:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 11:20 [PATCH 0/3] more doc about isolated mode and bifurcated model Thomas Monjalon
2019-01-30 11:20 ` [PATCH 1/3] doc: remove useless anchor for flow API guide Thomas Monjalon
2019-01-30 11:20 ` [PATCH 2/3] doc: add references to flow isolated mode in NICs guide Thomas Monjalon
2019-01-30 11:20 ` [PATCH 3/3] doc: improve Mellanox bifurcated model description Thomas Monjalon
2019-01-31 6:58 ` [PATCH 0/3] more doc about isolated mode and bifurcated model Shahaf Shuler
2019-01-31 17:36 ` 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=1918029.g09UHAWXCS@xps \
--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 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.