Skip to content

Conversation

komal-marvell
Copy link
Contributor

Metadata can be assigned on Router Interface and subsequently matched in ACL entries, providing increased flexibility for policy management.

typedef union _sai_acl_capability_extended_value_t
{
/** @validonly type == SAI_ACL_CAPABILITY_EXTENDED_TYPE_ROUTER_INTERFACE_META_DATA */
sai_u32_range_t router_interface_meta_data_range;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what happens if we want to add additional attributes in the future and need a bigger data type. This becomes again non binary compatible

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so this is a new complex mechanism, but seems not extendable
and in the end, do you really need different metadata range per stage ?
or can we just add new attribute like SAI_SWITCH_ATTR_ACL_USER_META_DATA_RANGE

@komal-marvell komal-marvell force-pushed the rif_meta branch 2 times, most recently from f1236f4 to 9e7d9da Compare September 25, 2025 07:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants