Currently, the routing types in DASH is used to define 2 things:
Stage transition: which stage we need to run as the next stage
Routing actions: what SDN transformations are required if this stage is the last stage used to match the packets.
Although the concepts are there, in DASH P4 code, these concepts are not reflected in a modularized way, and sometimes not that obvious as the transition cannot be found in the definitions of the routing types (P4 table actions).
What this change is doing
This commit contains 2 changes inside:
Add skeleton for matching stage transition control
Extract the matching stages in outbound pipeline into dedicated file
These changes are intended to help with:
Modularization and readability of the pipeline.
Make the stage transition control more explicit and obvious.
This commit will not change any generated SAI APIs.
Problem
Currently, the routing types in DASH is used to define 2 things:
Although the concepts are there, in DASH P4 code, these concepts are not reflected in a modularized way, and sometimes not that obvious as the transition cannot be found in the definitions of the routing types (P4 table actions).
What this change is doing
This commit contains 2 changes inside:
These changes are intended to help with:
This commit will not change any generated SAI APIs.