Meter update stage.

sonic-net · Oct 9, 2023 · 15ff98d · 15ff98d
1 parent f6e07bd
commit 15ff98d
Showing 1 changed file with 5 additions and 0 deletions.
diff --git a/documentation/general/dash-sai-pipeline-packet-flow.md b/documentation/general/dash-sai-pipeline-packet-flow.md
@@ -28,6 +28,7 @@
       4. [5.8.4. Action publishing](#584-action-publishing)
       5. [5.8.5. Metadata publishing](#585-metadata-publishing)
    9. [5.9. Action apply](#59-action-apply)
+   10. [5.10. Meter update](#510-meter-update)
 6. [6. Examples](#6-examples)
    1. [6.1. VNET routing](#61-vnet-routing)
    2. [6.2. VM level public IP inbound (L3 DNAT)](#62-vm-level-public-ip-inbound-l3-dnat)
@@ -583,6 +584,10 @@ This design also allows us to decouples the time of fulfilling the routing actio
 
 After all matching stages are done, we will start applying all the actions. All the latest values in the metadata bus will be used as the input parameters for the routing actions.
 
+### 5.10. Meter update
+
+After all actions are applied, post-pipeline ACLs are passed, we will update the metering counters if any metering class is specified.
+
 ## 6. Examples
 
 Here are some examples to demo how to apply the DASH-SAI pipeline to implement different network functions. They might not be up-to-date or complete policies, but mostly demoing the high level ideas.