From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v2] ethdev: add fuzzy match pattern Date: Thu, 08 Jun 2017 09:19:24 +0200 Message-ID: <2304112.MuvLPJetXV@xps> References: <1495582134-13665-1-git-send-email-qi.z.zhang@intel.com> <1496874080-35086-1-git-send-email-qi.z.zhang@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, adrien.mazarguil@6wind.com To: Qi Zhang Return-path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 85E022BB8 for ; Thu, 8 Jun 2017 09:19:27 +0200 (CEST) In-Reply-To: <1496874080-35086-1-git-send-email-qi.z.zhang@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi, 08/06/2017 00:21, Qi Zhang: > Add new meta pattern item RTE_FLOW_TYPE_ITEM_FUZZY. I disagree about fuzzy wording, because fuzzy is something different I think. > 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 two different patterns have the same hash value. You have described it yourself here: it matches a hash of the signature. Why not using "hash" as wording? > Matching accuracy level can be configure by subfield threshold. > Driver can divide the range of threshold and map to different > accuracy levels that device support. > > Signed-off-by: Qi Zhang