dipankar-ba

Hi Anandhi, Honestly I do not know about all MACsec implementations out there. This object relationship is accepted and used for years - so I didn't want to risk breaking...

There is no implicit relationship limiting a flow from being used for multiple ports. Multiple ACL entries can be bound to a MACsec flow, and those can belong to different...

> > There is no implicit relationship limiting a flow from being used for multiple ports. Multiple ACL entries can be bound to a MACsec flow, and those can belong...

Hi Anandhi, Perhaps you are right and nobody in their right mind would have shared a flow across ports. But in Sid's defense it is not him :-) Forgive the...

Attaching a port to SC will not cause trouble for existing drivers because a MACsec SC cannot support 2 ports. If a new driver needs to program per-port memory for...

Here are the reasons why this SAI counter deviates from the IEEE spec: 1. Per SA count is more granular than per SC count and can be useful for debugging...

1. For existing chips with only per-SA counter, if the API exposes both per-SC and per-SA counter then the driver has to construct counter states to support both per-SA and...

Just to be clear, as per existing API, the NOS should sum up the sai_macsec_sa_stat_octets_encrypted for all SAs of an SC. For a chip that implements per SC counter for...