Skip to content

QP routing - #2381

Open
j-bos wants to merge 2 commits into
opencomputeproject:masterfrom
j-bos:qp_routing
Open

j-bos wants to merge 2 commits into
opencomputeproject:masterfrom
j-bos:qp_routing

Conversation

@j-bos

@j-bos j-bos commented Nov 4, 2026 •

Copy link
Copy Markdown
Contributor

Introduce experimental API to enable routing paths to based on RoCE QP + DIP.

This enables a forwarding decision to be made based on QP + DIP routing entries, with fallback to regular DIP-based forwarding on miss.

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

Add QP routes keyed by switch, virtual router, QP ID, and destination prefix. Register a separate experimental API and object type using the existing metadata generation paths.

Signed-off-by: Jason Bos <jbos@cisco.com>
@j-bos
j-bos marked this pull request as ready for review November 5, 2026 00:15
@j-bos j-bos changed the title QP route API QP routing Nov 5, 2026
Signed-off-by: Jason Bos <jbos@cisco.com>
@tjchadaga tjchadaga added the reviewed PR is discussed in SAI Meeting label Nov 5, 2026
[`experimental/saiexperimentalqproute.h`](../experimental/saiexperimentalqproute.h).

## 2. Functional Behavior

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

QP routing would be a RIF property.
We should add a bool to enable/disable QP routing on a RIF.

Something like
/**
* @brief QP Route enable
*
* @type bool
* @flags CREATE_AND_SET
* @default false
*/
SAI_ROUTER_INTERFACE_ATTR_QP_ROUTE_ENABLE,

*
* @type sai_object_id_t
* @flags CREATE_AND_SET
* @objects SAI_OBJECT_TYPE_NEXT_HOP, SAI_OBJECT_TYPE_NEXT_HOP_GROUP, SAI_OBJECT_TYPE_ROUTER_INTERFACE, SAI_OBJECT_TYPE_PORT

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

given that the goal is to pin to an egress interface, should we avoid accepting SAI_OBJECT_TYPE_NEXT_HOP_GROUP here?

@JaiOCP

JaiOCP commented Nov 16, 2026 via email

Copy link
Copy Markdown
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

reviewed PR is discussed in SAI Meeting

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants