From patchwork Sun May 14 19:50:06 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Qi Zhang X-Patchwork-Id: 24283 Return-Path: X-Original-To: patchwork@dpdk.org Delivered-To: patchwork@dpdk.org Received: from [92.243.14.124] (localhost [IPv6:::1]) by dpdk.org (Postfix) with ESMTP id 0DA1E5942; Mon, 15 May 2017 04:56:33 +0200 (CEST) Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 929685398 for ; Mon, 15 May 2017 04:56:27 +0200 (CEST) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 May 2017 19:56:26 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.38,342,1491289200"; d="scan'208";a="856781551" Received: from unknown (HELO localhost.localdomain.sh.intel.com) ([10.239.129.189]) by FMSMGA003.fm.intel.com with ESMTP; 14 May 2017 19:56:25 -0700 From: Qi Zhang To: adrien.mazarguil@6wind.com Cc: dev@dpdk.org, wenzhuo.lu@intel.com, beilei.xing@intel.com, Qi Zhang Date: Sun, 14 May 2017 15:50:06 -0400 Message-Id: <1494791406-3594-3-git-send-email-qi.z.zhang@intel.com> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1494791406-3594-1-git-send-email-qi.z.zhang@intel.com> References: <1494791406-3594-1-git-send-email-qi.z.zhang@intel.com> Subject: [dpdk-dev] [RFC 2/2] doc/guides/prog_guide: add new flow attribute 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Update the programming guide for the new attribute of rte_flow Signed-off-by: Qi Zhang --- 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. + Pattern item ~~~~~~~~~~~~