From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dispatch1-us1.ppe-hosted.com (dispatch1-us1.ppe-hosted.com [67.231.154.164]) by dpdk.org (Postfix) with ESMTP id 545E57EC7 for ; Wed, 17 Oct 2018 16:05:49 +0200 (CEST) X-Virus-Scanned: Proofpoint Essentials engine Received: from webmail.solarflare.com (uk.solarflare.com [193.34.186.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mx1-us3.ppe-hosted.com (Proofpoint Essentials ESMTP Server) with ESMTPS id 94B219C04EF; Wed, 17 Oct 2018 14:05:46 +0000 (UTC) Received: from [192.168.38.17] (91.220.146.112) by ukex01.SolarFlarecom.com (10.17.10.4) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 17 Oct 2018 15:05:37 +0100 To: Dekel Peled , , , , , , , CC: , , References: <1539254998-8555-1-git-send-email-dekelp@mellanox.com> <1539777829-64412-2-git-send-email-dekelp@mellanox.com> From: Andrew Rybchenko Message-ID: Date: Wed, 17 Oct 2018 17:04:56 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <1539777829-64412-2-git-send-email-dekelp@mellanox.com> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB X-Originating-IP: [91.220.146.112] X-ClientProxiedBy: ocex03.SolarFlarecom.com (10.20.40.36) To ukex01.SolarFlarecom.com (10.17.10.4) X-TM-AS-Product-Ver: SMEX-12.5.0.1300-8.5.1010-24160.003 X-TM-AS-Result: No-5.981900-8.000000-10 X-TMASE-MatchedRID: u1zqiMeMcroOwH4pD14DsPHkpkyUphL9wx0jRRxcQfP4JyR+b5tvoLB6 KjveEuzJYREd+vD/UBFYFBU0+2PUKQ4mAn6Exf2OngIgpj8eDcC063Wh9WVqgtQdB5NUNSsi1Gc RAJRT6POOhzOa6g8KrQ/1vRFEWeMefMNqrhMUMf28hdL5hcQeYEipKAOsAggl7tR7/cBU9BccZA nxwF1bsmn1H5ZPbi+4sxDP8j1n+CuMg6RCFrlf0OL59MzH0po2K2yzo9Rrj9wPoYC35RuihKPUI 7hfQSp5eCBcUCG1aJiUTGVAhB5EbQ== X-TM-AS-User-Approved-Sender: Yes X-TM-AS-User-Blocked-Sender: No X-TMASE-Result: 10--5.981900-8.000000 X-TMASE-Version: SMEX-12.5.0.1300-8.5.1010-24160.003 X-MDID: 1539785148-XWQBOw-GKk7F Subject: Re: [dpdk-dev] [PATCH v5 1/3] ethdev: support metadata as flow rule criteria 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: Wed, 17 Oct 2018 14:05:49 -0000 On 10/17/18 3:03 PM, Dekel Peled wrote: > As described in [1], a new rte_flow item is added to support metadata > to use as flow rule match pattern. > The metadata is an opaque item, fully controlled by the application. > > The use of metadata is relevant for egress rules only. > It can be set in the flow rule using the RTE_FLOW_ITEM_META. > > An additional member 'tx_metadata' is added in union with existing member > 'hash' of struct 'rte_mbuf', located to avoid conflicts with existing > fields. This additional member is used to carry the metadata item. > > Application should set the packet metadata in the mbuf dedicated field, > and set the PKT_TX_METADATA flag in the mbuf->ol_flags. > The NIC will use the packet metadata as match criteria for relevant > flow rules. > > This patch introduces metadata item type for rte_flow RTE_FLOW_ITEM_META, > along with corresponding struct rte_flow_item_meta and ol_flag > PKT_TX_METADATA. > > [1] "[RFC,v2] ethdev: support metadata as flow rule criteria" > > Signed-off-by: Dekel Peled Acked-by: Andrew Rybchenko