From mboxrd@z Thu Jan 1 00:00:00 1970 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) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id F3FB120A6C; Thu, 8 Jun 2017 03:19:25 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Thu, 08 Jun 2017 03:19:26 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=ZX2Tnl3/10kOPu9 W4Kkz8k+lMUPUZp0fX1R6ssvkQds=; b=hx9vlfVnX2YciyJEyywsKke2h9u0Dhp Ir6jh5ELcaBXGg8UegGvFww/3S3ivn1nE2vUXO/rTnf/dMrvs3hVwALbWdQrrPiO RrpJe0ue7Ssa6Yo6Ox2P8NFV5R+o/cYkzG1w6SNBcJEP0H3W35yFl2zjFJnILj9J pbXKE1NhbsP4= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=ZX2Tnl3/10kOPu9W4Kkz8k+lMUPUZp0fX1R6ssvkQds=; b=ZJjrsyuo 9gXGrQZG+bmrIkkViTHhEXja4XLgdwkBPzxKx1vi9g7Nn6Gya4h4LNwpVruok6AN mITds/iZ3ccoPRA/YbHW2fxT5oPgRn2bgFkKNKyoo5fhKeQAiHMedlypsd7IIXqy j76ohFaNuoVtBOrVoEwxy7HDXfv3l/kgl0/HyB1Xrtw8+FjNLNjBkYZcrVmLO0RE 3VN9Gm6sUVA1cUBSLfV3J7FH2GRPjH+KVa3H0Vn/yNU6Ax0xlkIu0qGDt/I5HF9h EO4R/peGWByrpwxsbpyrIvS1cl0CDi38xC5UFD6nqYyybEa7daucm1U1v80BvJR6 OvbTL5BnI3Z0Hg== X-ME-Sender: X-Sasl-enc: /I6gov2DT/Sd+v6cIDLz1+U6V+rilVX1s7ThxNpMcllu 1496906365 Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id A974E2486C; Thu, 8 Jun 2017 03:19:25 -0400 (EDT) From: Thomas Monjalon To: Qi Zhang Cc: dev@dpdk.org, adrien.mazarguil@6wind.com Date: Thu, 08 Jun 2017 09:19:24 +0200 Message-ID: <2304112.MuvLPJetXV@xps> In-Reply-To: <1496874080-35086-1-git-send-email-qi.z.zhang@intel.com> 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-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v2] ethdev: add fuzzy match pattern X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jun 2017 07:19:27 -0000 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