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 <adrien.mazarg...@6wind.com> --- 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
