From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id 7166D1B1DA for ; Thu, 21 Dec 2017 05:44:27 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 20 Dec 2017 20:44:26 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.45,434,1508828400"; d="scan'208";a="17790347" Received: from dpdk27.sh.intel.com ([10.67.111.90]) by orsmga001.jf.intel.com with ESMTP; 20 Dec 2017 20:44:24 -0800 From: Qi Zhang To: adrien.mazarguil@6wind.com Cc: dev@dpdk.org, declan.doherty@intel.com, Qi Zhang Date: Wed, 20 Dec 2017 16:34:44 -0500 Message-Id: <1513805689-28202-1-git-send-email-qi.z.zhang@intel.com> X-Mailer: git-send-email 2.7.4 Subject: [dpdk-dev] [RFC 0/5] rte_flow extension for vSwitch acceleration 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, 21 Dec 2017 04:44:28 -0000 This patch extend rte_flow API. The purpose is to provide comfortable programming interface for virtual switch software (such as OVS) to take advantage of incoming device's vSwitch acceleration capability when using DPDK as data plane. Below is summary of changes: 1. Support to specify flow's destination as an ethdev interface. Add action RTE_FLOW_ACTION_TYPE_ETHDEV_PORT, use port_id as the identification of the destitation. A typical use case is, with a smart NIC used for vSwitch acceleration, flow is defined to redirect packet between switch port that is managed by a Port Representor. See patch for Port Representor: http://dpdk.org/dev/patchwork/patch/31458/ 2. Enhanced flow statistics query. Enhanced action RTE_FLOW_ACTION_COUNT by adding last hit timestamp tracking which is the requirement from OVS. 3. Add flow timeout support as the requirement from OVS Application is able to a) Setup the time duration of a flow, the flow is expected to be deleted automatically when timeout. b) Ping a flow to check if it is active or not. c) Register a callback function when a flow is deleted due to timeout. 4. Add protocol headers which will be supported by incoming device. New protocal headers include IPV4 ARP, IPV6 ICMP , IPV6 extent header. 5. Add packet modification actions which will be supported by incoming device. Add new actions that be used to modify packet content with generic semantic: RTE_FLOW_ACTION_TYPE_FIELD_UPDATE: update specific field of packet RTE_FLWO_ACTION_TYPE_FIELD_INCREMENT: increament specific field of packet RTE_FLWO_ACTION_TYPE_FIELD_DECREMENT: decreament specific field of packet RTE_FLWO_ACTION_TYPE_FIELD_COPY: copy data from one field to another in packet. All action use struct rte_flow_item parameter to match the pattern that going to be modified, if no pattern match, the action just be skipped. These action are non-terminating action. they will not impact the fate of the packets, since pattern match is expected to be performed before packet be modified. Note: The RFC patch is based on v17.11. Testpmd command line support is not included. Qi Zhang (4): ether: add flow action to redirect packet in a switch domain ether: add flow last hit query support ether: Add flow timeout support ether: add packet modification aciton in rte_flow Thomas Monjalon (1): version: 17.11.0 doc/guides/prog_guide/rte_flow.rst | 148 +++++++++++++++++++++++++++ lib/librte_eal/common/include/rte_version.h | 4 +- lib/librte_ether/rte_flow.c | 38 +++++++ lib/librte_ether/rte_flow.h | 149 +++++++++++++++++++++++++++- lib/librte_ether/rte_flow_driver.h | 12 +++ pkg/dpdk.spec | 2 +- 6 files changed, 349 insertions(+), 4 deletions(-) -- 2.7.4