From: Thomas Monjalon <thomas@monjalon.net>
To: Qi Zhang <qi.z.zhang@intel.com>
Cc: dev@dpdk.org, adrien.mazarguil@6wind.com
Subject: Re: [PATCH v3] ethdev: add fuzzy match in flow API
Date: Wed, 05 Jul 2017 19:55:02 +0200 [thread overview]
Message-ID: <1654286.Y8MLXh4jVJ@xps> (raw)
In-Reply-To: <1497323225-16618-1-git-send-email-qi.z.zhang@intel.com>
13/06/2017 05:07, Qi Zhang:
> Add new meta pattern item RTE_FLOW_TYPE_ITEM_FUZZY in flow API.
>
> This is for device that support fuzzy match option.
> Usually a fuzzy match is fast but the cost is accuracy.
> i.e. Signature Match only match pattern's hash value, but it is
> possible that two different patterns have the same hash value.
>
> Matching accuracy level can be configured by subfield threshold.
> Driver can divide the range of threshold and map to different
> accuracy levels that device support.
>
> Signed-off-by: Qi Zhang <qi.z.zhang@intel.com>
Applied, thanks
next prev parent reply other threads:[~2017-07-05 17:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 23:28 [PATCH] ethdev: add roughly match pattern Qi Zhang
2017-05-30 12:46 ` Adrien Mazarguil
2017-05-31 7:51 ` Gaëtan Rivet
2017-06-01 1:44 ` Zhang, Qi Z
2017-06-01 14:44 ` Adrien Mazarguil
2017-06-07 22:21 ` [PATCH v2] ethdev: add fuzzy " Qi Zhang
2017-06-08 7:19 ` Thomas Monjalon
2017-06-12 15:38 ` Adrien Mazarguil
2017-06-13 6:03 ` Zhang, Qi Z
2017-06-13 3:07 ` [PATCH v3] ethdev: add fuzzy match in flow API Qi Zhang
2017-07-05 16:06 ` Ferruh Yigit
2017-07-05 17:55 ` Thomas Monjalon [this message]
2017-06-21 19:07 ` [PATCH v3 0/3] net/ixgbe: enable signature match and ipv6 for consistent API Qi Zhang
2017-06-21 19:07 ` [PATCH v3 1/3] net/ixgbe: replace macro with inline function Qi Zhang
2017-06-21 19:07 ` [PATCH v3 2/3] net/ixgbe: enable signature match for consistent API Qi Zhang
2017-06-21 19:07 ` [PATCH v3 3/3] net/ixgbe: enable IPv6 " Qi Zhang
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=1654286.Y8MLXh4jVJ@xps \
--to=thomas@monjalon.net \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@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.