Policer enhancement to support operational visibility and MEF Metering Modes - #2323
Policer enhancement to support operational visibility and MEF Metering Modes#2323AnandhiDhanabalan wants to merge 2 commits into
Conversation
Signed-off-by: Anandhi Dhanabalan <adhanabalan@marvell.com>
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
Signed-off-by: Anandhi Dhanabalan <adhanabalan@marvell.com>
|
@kcudnik, I'd like to add an alias similar to the one below. However, I get a compilation error because two enum values resolve to the same value. Is there a way to support enum aliases in this case? SAI_POLICER_MODE_TR_TCM_V2 = 0x00000003,
/** MEF 10.2 with Coupling Flag = 0 (RFC 4115 compliant) */
SAI_POLICER_MODE_MEF0 = SAI_POLICER_MODE_TR_TCM_V2, |
|
why you want to add alias if you have explicit name for that alreay? add "@ignore" to this enum |
Current SAI supports only
Is supporting such enum aliases possible? |
yes |
Can I update the PR even if warning/error for same comes when |
|
yes, you can force push |
Overview
This proposal enhances the SAI policer specification by introducing capabilities that improve operational transparency and broaden deployment readiness for carrier Ethernet environments.
Key Enhancements
1. Addition of MEF Standard Metering Modes
Introduce support for MEF 10.2 metering algorithms (MEF0 / MEF1), widely adopted in service provider and metro Ethernet networks. This expands SAI policer capabilities to align with established carrier bandwidth profiling models.
2. Improved Hardware Configuration Visibility
Provide a standard mechanism to query the actual CIR / PIR / CBS / PBS values programmed in hardware. This gives operators clear insight into effective policer settings, helping validate SLA targets, understand hardware-applied values, and simplify troubleshooting.