From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f65.google.com (mail-wm0-f65.google.com [74.125.82.65]) by dpdk.org (Postfix) with ESMTP id 31E441B2C1 for ; Wed, 14 Feb 2018 16:37:43 +0100 (CET) Received: by mail-wm0-f65.google.com with SMTP id j199so11338573wmj.2 for ; Wed, 14 Feb 2018 07:37:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=7XfgmCUt60S7DNyOaU/T3gXL8Z29Rpwpf8UrQgCtfbc=; b=zizuIPeiiYqxmOIf9vshUfLZT0OohkCLzaQ/S2vMYgrCYDwb5rFmPp7mEMcQb9dWhD eBd+7XGoASK9TwjOuxoG6QNA1zUaY7CuqG6OsTHFsafwDwnA84HySPcxxMYJpxNwXGph Y4NRAuGKthDhTWpKbEjdCUitXzGcqUEngS5kFgremafk5DK0ZxcGHnie61+Rt++cjELS fYYlx9gt0+4mamEJkLe3f2LV4+49RFB0trKZxwAXevyRpzWs5yUZ1s5KZ8mr0ZWUp4hi pDnSEUYxvFZqejP1fG95smyMBuOlbhX4CRQ1/nufA18ssUv3eWaZA3ctszFGAJtrY11d pJPw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=7XfgmCUt60S7DNyOaU/T3gXL8Z29Rpwpf8UrQgCtfbc=; b=og/31br/Zp05JcHeWJuKiLxiAyVG2wCnnZAX3UR8FhKQSgUKX6yRxI47xQ/IWA5ViD HLHpBXrxARhI0UfgcHl5dqh5cTVSuJALb5yLDQfXIUpV0c62RV6X35dVxPkr4VGvZ7Il noI8RJf1mtjfvnMrXyJvaD633HwGfp0q5acNm5ks+u8qfBbh4IM6W/UsXB5UYnL/ROd/ 4PNxBU+b2W84ZVEZc/NVkowroKpr7/3jdSpHNn7QcCk7fTHodwvsityzI1Rvc/GpmBrC yyi1GWIDtvzUvDHjmYQ4sIXgDBZ0Yo3523boYaSnTimhew7OUmVgFebEQfkwRYKIu1Lp JrPw== X-Gm-Message-State: APf1xPAgN+mS9KamZc6nIIER9QYnoIZfZEL++WjONXZkcRmQx+RO1Jtd drjBPPVLu+Rx81+fO4nicOQ2hw== X-Google-Smtp-Source: AH8x22763WbCN+2UNBY2GR6iyqJJhfKviaYRXAY9XNQvOpdTdYyw56/D8I0FL0fszIkMouJPSmhp1w== X-Received: by 10.28.66.77 with SMTP id p74mr2758614wma.115.1518622662910; Wed, 14 Feb 2018 07:37:42 -0800 (PST) Received: from 6wind.com (host.78.145.23.62.rev.coltfrance.com. [62.23.145.78]) by smtp.gmail.com with ESMTPSA id k13sm11642934wrd.61.2018.02.14.07.37.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 14 Feb 2018 07:37:42 -0800 (PST) Date: Wed, 14 Feb 2018 16:37:29 +0100 From: Adrien Mazarguil To: Neil Horman Cc: Ferruh Yigit , dev@dpdk.org, "Doherty, Declan" , Shahaf Shuler , "John Daley (johndale)" , Nelio Laranjeiro , "Xueming(Steven) Li" , Thomas Monjalon Message-ID: <20180214152847.19774-2-adrien.mazarguil@6wind.com> References: <20180214152847.19774-1-adrien.mazarguil@6wind.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180214152847.19774-1-adrien.mazarguil@6wind.com> X-Mailer: git-send-email 2.11.0 Subject: [dpdk-dev] [PATCH v1 1/4] doc: announce API change for flow actions 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, 14 Feb 2018 15:37:43 -0000 This announce is related to the discussion regarding TEP and the need for encap/decap support in rte_flow [1]. It's now clear that PMD support for chaining multiple non-terminating flow rules of varying priority levels is prohibitively difficult to implement compared to simply allowing multiple identical actions performed in a defined order by a single flow rule. [1] http://dpdk.org/ml/archives/dev/2017-December/084676.html Signed-off-by: Adrien Mazarguil --- doc/guides/rel_notes/deprecation.rst | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst index d59ad5988..663550acb 100644 --- a/doc/guides/rel_notes/deprecation.rst +++ b/doc/guides/rel_notes/deprecation.rst @@ -59,3 +59,11 @@ Deprecation Notices be added between the producer and consumer structures. The size of the structure and the offset of the fields will remain the same on platforms with 64B cache line, but will change on other platforms. + +* rte_flow: flow rule action semantics will be modified to enable support + for encap/decap. All actions part of a flow rule will be taken into + account; not only the last one in case of repeated actions. Their order + will matter. This change will make the DUP action redundant, and the + (non-)terminating property of actions will be discarded. Instead, flow + rules themselves will be considered terminating by default unless a + PASSTHRU action is also specified. -- 2.11.0