Switching ASICs SDKs do not have any common API Same feature for eg Routing Table has different styles Same underlying construct for eg ACL has different semantics SAI addresses above issue and offers a C API thats common across ASICs ID: 725059
Download Presentation The PPT/PDF document "OCP SAI Sanjay Sane OCP SAI" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
OCP SAI
Sanjay SaneSlide2
OCP SAI
Switching ASICs (SDKs) do not have any common API.
Same feature (for e.g. Routing Table) has different styles.
Same underlying construct (for e.g. ACL) has different semantics.
SAI addresses above issue, and offers a C API that’s common across ASICs.
Identifies the switching abstraction, express it as {object,
attribute:value
}
Open API, is extensible for newer abstractions and programmable ASICs.
SAI does not deal with specifying user-APIs or defining user-models.
Note that many of these user-APIs end up using overlapping hardware abstractions.
Thus, SAI is a way to express hardware/ASIC constructs in an abstracted fashion, and provide a unified API across plethora of
silicons
/platforms.
SAI
is an open
initiative (
https://
github.com/opencomputeproject/OCP-Networking-Project-Community-Contributions/tree/master/sai/inc
).
OCP-compliant platform will have SAI driver. Slide3
Thank you