parent a40cfa9

author JaiOCP <jai.kumar@broadcom.com> 1780351110 -0700
committer JaiOCP <jai.kumar@broadcom.com> 1781547347 -0700

Optimized Forwarding Header

Signed-off-by: JaiOCP <jai.kumar@broadcom.com>

Optimized Forwarding Header

Signed-off-by: JaiOCP <jai.kumar@broadcom.com>

Fix gensairpc.pl crash on Doxygen 1.9.8+ by reusing NeedsTwoPassProcessing (#2282)

Why:
To fix below build error

Uncaught exception from user code:
	 at gensairpc.pl line 480.
		main::assign_attr_types(HASH(0x55e190dc20c8), ARRAY(0x55e190d2d080)) called at gensairpc.pl line 434
		main::get_definitions() called at gensairpc.pl line 156
	main::assign_attr_types(HASH(0x55e190dc20c8), ARRAY(0x55e190d2d080)) called at gensairpc.pl line 434
	main::get_definitions() called at gensairpc.pl line 156

How:
gensairpc.pl crashed during SAI thrift build with an uncaught exception
at line 480 (assign_attr_types) because its inline Doxygen layout
detection was too weak - it only checked sai_8h.xml for any enumvalue
presence, missing cases where the new Doxygen 1.9.8+ XML structure
requires group__*.xml files to be processed for complete definitions.
This caused incomplete parsing, leading to missing types and a croak
in assign_attr_types when sai_attribute_value_t could not be found.

Changes:
- xmlutils.pm: Add NeedsTwoPassProcessing and export it.
- parse.pl: Remove local NeedsTwoPassProcessing; use imported version.
- gensairpc.pl: Replace inline detection with NeedsTwoPassProcessing()
  call, fixing the build failure and eliminating code duplication.

Signed-off-by: Pavan Naregundi <pnaregundi@marvell.com>

Count BFD session state changes from UP to DOWN (#2268)

Signed-off-by: Chikkegowda Chikkaiah <cchikkai@cisco.com>

SAI API Performance Monitoring (#2287)

Signed-off-by: JaiOCP <jai.kumar@broadcom.com>

Support OTN attenuator and amplifier (#2217)

1. Add a new precision attribute flag for optical analog values (e.g., gain, tilt, power), instead of using double/float point type which would introduce NaN issue.
2. Add support for optical attenuator in experimental extensions, derived from openconfig-optical-attenuator.yang.
3. Add support for optical amplifier in experimental extensions, derived from openconfig-optical-amplifier.yang.
4. Add SAI extension for OTN proposal document.

Signed-off-by: Jimmy Jin <jjin62@yahoo.com>
Co-authored-by: Lu.Mao <lu.mao@molex.com>

OFH Admin State

Signed-off-by: JaiOCP <jai.kumar@broadcom.com>

Author: JaiOCP

doc/OTN/images/SAI_with_OTN_objects.png

@@ -0,0 +1,237 @@
+# Performance Monitoring SAI Specification
+-------------------------------------------------------------------------------
+ Title       | SAI support for Performance Monitoring
+:-------------|:-----------------------------------------------------------------
+ Authors     | Jai Kumar, Broadcom Inc
+ Status      | In review
+ Type        | Standards track
+ Created     | 03/18/2026: Initial Draft
+ SAI-Version | 1.19
+-------------------------------------------------------------------------------
+
+
+## 1.0  Introduction
+As network fabric scale increases and data centers require regional spine connectivity, the number of downlinks for cluster connectivity is growing. This leads to more LAGs, more prefixes, and larger ECMP. This is also true for large scale up and scale across fabrics for AI/ML.
+
+This increasing scale mandates that SAI be scalable, reliable, and high-performance. This specification addresses the performance component of SAI by introducing a new set of metrics to accurately measure the performance of various components within the SAI layer and below, such as SDK and hardware updates.
+
+Using these metrics, deployments can isolate components impacting performance and focus on their optimization.
+
+
+
+## 2.0 Terms and Acronyms
+
+| Term| Description | 
+|:---|:---|
+| perfmon | Performance Metrics  |
+
+## 3.0 Overview
+The SAI infrastructure exposes a set of APIs as a standard interface to the upper layer.
+
+These APIs are synchronous and blocking, making the completion time of any given API a critical performance measure. Note that application-specific callbacks are not addressed by this specification.
+
+```
+/**
+ * @brief SAI common API type
+ */
+typedef enum _sai_common_api_t
+{
+    SAI_COMMON_API_CREATE      = 0,
+    SAI_COMMON_API_REMOVE      = 1,
+    SAI_COMMON_API_SET         = 2,
+    SAI_COMMON_API_GET         = 3,
+    SAI_COMMON_API_BULK_CREATE = 4,
+    SAI_COMMON_API_BULK_REMOVE = 5,
+    SAI_COMMON_API_BULK_SET    = 6,
+    SAI_COMMON_API_BULK_GET    = 7,
+    SAI_COMMON_API_MAX         = 8,
+} sai_common_api_t;
+
+```
+
+This specification proposes API performance measures for the following metrics
+1. Average Latency
+2. Instantaneous Latency
+3. Maximum Latency
+
+### 3.1 Average, Instantaneous, and Maximum Latency
+API completion time consists of the time spent in the SAI adapter and the SDK, including hardware update or query time. Time measured is irrespetcive of the status of the API call i.e. if the API call completes with error status, adapter will still account the measured latency during the time interval of the metrics computation. NOS tracks the return status of API calls and can account for errors as needed. Discounting latency for specific error statuses would result in inconsistent measurements, requiring metric subscribers to implement manual workarounds for those cases.
+
+These metrics can be used to: 
+- Improve SAI adapter and SDK implementations
+- Provide a baseline for comparing different hardware
+- Instantaneous value: last observed latency for the API call
+- Maximum: The highest value observed across the last n invocations
+- Average: The average value over the last n invocations.
+
+
+## 4.0 SAI Specification 
+New perfmon object is introduced. Each perfmon object specifies the object of interest, set of APIs and metrics to be measured for each API.
+
+
+Each perfmon object created has a binding to the switch object.
+
+### 4.2 Perfmon Object
+New perfmon object is introduced specifying API and metrics of interest.
+
+#### 4.3.1 Metrics
+Each API can be measure for a specific performance metrics as specified in sai_perfmon_metrics_t
+
+```
+/**
+ * @brief Performance Monitoring Metrics
+ */
+typedef enum _sai_perfmon_metrics_t
+{
+    /**
+     * @brief None
+     */
+    SAI_PERFMON_METRICS_NONE,
+
+    /**
+     * @brief Maximum latency observed
+     */
+    SAI_PERFMON_METRICS_MAX_LATENCY,
+
+    /**
+     * @brief Average latency observed
+     */
+    SAI_PERFMON_METRICS_AVERAGE_LATENCY,
+
+    /**
+     * @brief Instantaneous latency observed
+     */
+    SAI_PERFMON_METRICS_INST_LATENCY,
+
+} sai_perfmon_metrics_t;
+
+```
+
+#### 4.3.2 Perfmon Object Attributes
+Type of API to be monitored for performance and its associated attributes are specified in the perfmon object attributes
+
+```
+/**
+ * @brief Performance Monitoring Attributes
+ */
+typedef enum _sai_perfmon_attr_t
+{
+    /**
+     * @brief Start of Attributes
+     */
+    SAI_PERFMON_ATTR_START,
+
+    /**
+     * @brief Object to be monitored
+     *
+     * @type sai_object_type_t
+     * @flags MANDATORY_ON_CREATE | CREATE_ONLY
+     */
+    SAI_PERFMON_ATTR_OBJECT_TYPE = SAI_PERFMON_ATTR_START,
+
+    /**
+     * @brief API to be monitored
+     *
+     * @type sai_common_api_t
+     * @flags CREATE_AND_SET
+     */
+    SAI_PERFMON_ATTR_COMMON_API,
+
+    /**
+     * @brief Performance metrics to be collected
+     *
+     * @type sai_perfmon_metrics_t
+     * @flags CREATE_AND_SET
+     * @default SAI_PERFMON_METRICS_NONE
+     */
+    SAI_PERFMON_ATTR_PERFMON_METRICS,
+
+    /**
+     * @brief Performance data as collected. This is clear on read.
+     * Performance data is computed once enabled and is cleared once read.
+     *
+     * @type sai_uint64_t
+     * @flags READ_ONLY
+     */
+    SAI_PERFMON_ATTR_PERFDATA,
+
+    /**
+     * @brief End of Performance Monitoring attributes
+     */
+    SAI_PERFMON_ATTR_END,
+
+    /** Custom range base value */
+    SAI_PERFMON_ATTR_CUSTOM_RANGE_START = 0x10000000,
+
+    /** End of custom range base */
+    SAI_PERFMON_ATTR_CUSTOM_RANGE_END
+
+} sai_perfmon_attr_t;
+
+```
+
+#### 4.3.3 Perfmon Object Switch Binding
+List of perfmon objects configured can be read using the following switch atribute.
+
+```
+    /**
+     * @brief Performance Monitoring enabled on the switch
+     *
+     * @type sai_object_list_t
+     * @flags READ_ONLY
+     * @objects SAI_OBJECT_TYPE_PERFMON
+     */
+    SAI_SWITCH_ATTR_PERFMON_LIST,
+```
+
+
+## 5.0 Sample Workflow
+
+This section talks about enabling performance monitoring for a given API and a metrics.
+
+### 5.1 Create perfmon object
+- Each perfmon object supports a single API and a single set of metrics. To monitor additional metrics for the same API or to monitor a different API, a new perfmon object must be created.
+- Monitoring in the SAI adapter will only begin once the perfmon object is bound to the switch object.
+
+```
+/*
+ * Configure Perfmon object for Bulk Set API performance monitoring
+ */
+
+// Specify the Object of intererst
+sai_attr_list[0].id = SAI_PERFMON_ATTR_OBJECT_TYPE;
+sai_attr_list[0].value.s32 = SAI_OBJECT_TYPE_ROUTE_ENTRY;
+
+// Specify the API of interest
+sai_attr_list[1].id = SAI_PERFMON_ATTR_COMMON_API;
+sai_attr_list[1].value.s32 = SAI_COMMON_API_BULK_SET;
+
+// Configure metrics to be measured
+sai_attr_list[2].id = SAI_PERFMON_ATTR_PERFMON_METRICS;
+sai_attr_list[2].value.s32 = SAI_PERFMON_METRICS_AVERAGE_LATENCY;
+
+// Create perfmon object
+attr_count = 3;
+create_perfmon(
+	&sai_perfmon_object,
+	switch_id, 
+	attr_count, 
+	sai_attr_list);
+```
+
+### 5.2 Read perfmon Metrics
+
+Read the perfmon attribute for getting the API related metrics.
+
+```
+// Specify the read attribute
+sai_attr_list[1].id = SAI_PERFMON_ATTR_PERFDATA;
+
+// Read perfmon metrics
+attr_count = 1;
+get_perfmon_attribute(
+	sai_perfmon_object,
+	attr_count, 
+	sai_attr_list);
+...
+