Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hostif trap type for Subnet routes #2066

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

rck-innovium
Copy link
Contributor

Fixes #2037 

When an IP address and subnet, say 10.1.1.1/24 is on a RIF and a neighbor 10.1.1.2 is learnt, the following set of routes are needed:

  1. 10.1.1.1/32 to CPU using SAI_HOSTIF_TRAP_TYPE_IP2ME,
  2. 10.1.1.1/24 route : This route points to CPU when NOS wants hints to trigger ARP requests. Some NOS implementations can choose to blackhole this route. Today, SAI does not let the NOS control- whether this packets should be dropped or trapped, and more importantly when it is trapped it neither allows the user to rate-limit this traffic nor select the CPU queue.
  3. 10.1.1.2/32 route: to the learnt neighbor

inc/saihostif.h Outdated Show resolved Hide resolved
Fixes opencomputeproject#2037

Signed-off-by: rck-innovium <rck@marvell.com>
@tjchadaga
Copy link
Collaborator

@JaiOCP, @marian-pritsak - could you please help sign off on this?

Copy link
Contributor

@JaiOCP JaiOCP left a comment

Choose a reason for hiding this comment

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

Lets discuss in community meeting to close on this.

@rlhui rlhui added the reviewed PR is discussed in SAI Meeting label Sep 19, 2024
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.

Hostif Trap for route to interface (subnet route)
4 participants