BCM doesn't care about clone sessions as clone_to_cpu-like table actions are manually mapped to the corresponding primitive in SDKLT, however, for it to be P4Runtime-compliant stratum_bcm should support reading and writing clone sessions. It's ok if we support only writing/reading one clone session for just the CPU port with a known session ID (hardcoded in the P4 program), internally handled as a no-op.
BCM doesn't care about clone sessions as
clone_to_cpu
-like table actions are manually mapped to the corresponding primitive in SDKLT, however, for it to be P4Runtime-compliantstratum_bcm
should support reading and writing clone sessions. It's ok if we support only writing/reading one clone session for just the CPU port with a known session ID (hardcoded in the P4 program), internally handled as a no-op.