DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Zhang, Qi Z" <qi.z.zhang@intel.com>,
	"adrien.mazarguil@6wind.com" <adrien.mazarguil@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
	"Xing, Beilei" <beilei.xing@intel.com>,
	"Zhang, Qi Z" <qi.z.zhang@intel.com>
Subject: Re: [dpdk-dev] [RFC 2/2] doc/guides/prog_guide: add new flow attribute
Date: Tue, 16 May 2017 09:11:27 +0000	[thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2332E0B2B@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <1494791406-3594-3-git-send-email-qi.z.zhang@intel.com>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Qi Zhang
> Sent: Sunday, May 14, 2017 8:50 PM
> To: adrien.mazarguil@6wind.com
> Cc: dev@dpdk.org; Lu, Wenzhuo <wenzhuo.lu@intel.com>; Xing, Beilei
> <beilei.xing@intel.com>; Zhang, Qi Z <qi.z.zhang@intel.com>
> Subject: [dpdk-dev] [RFC 2/2] doc/guides/prog_guide: add new flow
> attribute
> 
> Update the programming guide for the new attribute of rte_flow
> 
> Signed-off-by: Qi Zhang <qi.z.zhang@intel.com>
> ---
>  doc/guides/prog_guide/rte_flow.rst | 12 ++++++++++++
>  1 file changed, 12 insertions(+)
> 
> diff --git a/doc/guides/prog_guide/rte_flow.rst
> b/doc/guides/prog_guide/rte_flow.rst
> index b587ba9..5207eec 100644
> --- a/doc/guides/prog_guide/rte_flow.rst
> +++ b/doc/guides/prog_guide/rte_flow.rst
> @@ -181,6 +181,18 @@ directions. At least one direction must be specified.
>  Specifying both directions at once for a given rule is not recommended
> but  may be valid in a few cases (e.g. shared counters).
> 
> +Attribute: Match hint
> +^^^^^^^^^^^^^^^^^^^^^
> +
> +This is a attribute to hint different pattern match accuracy.
> +
> +Perfect match:
> +- Actions will be taken if input packet's pattern matches flow's pattern.
> +
> +Signature match:
> +- Actions will be taken if the signature of input packet's pattern
> +matches
> +  the signature of flow's pattern.
> +

There should be a blank line before the list items, otherwise it will
cause an RST warning.

  reply	other threads:[~2017-05-16  9:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-14 19:50 [dpdk-dev] [RFC 0/2] ethdev: add new attribute for signature match Qi Zhang
2017-05-14 19:50 ` [dpdk-dev] [RFC 1/2] rte_flow: add " Qi Zhang
2017-05-14 19:50 ` [dpdk-dev] [RFC 2/2] doc/guides/prog_guide: add new flow attribute Qi Zhang
2017-05-16  9:11   ` Mcnamara, John [this message]
2017-05-17 10:32 ` [dpdk-dev] [RFC 0/2] ethdev: add new attribute for signature match Adrien Mazarguil

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=B27915DBBA3421428155699D51E4CFE2332E0B2B@IRSMSX104.ger.corp.intel.com \
    --to=john.mcnamara@intel.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=qi.z.zhang@intel.com \
    --cc=wenzhuo.lu@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).