You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the IPDK build (in particular, the P4-DPDK backend) builds a lot of dependent packages:
P4-OVS
p4runtime
stratum
protobuf
SAI
P4C compiler
P4-DPDK
DPDK
TDI
target-syslibs
target-utils
Ideally, we would move to a world where each of those build targets generate their own packages, and IPDK becomes the CLI to manage IPDK container images, and any glue logic required to build the IPDK containers. In this world, we're not pulling down and building everything each and every time, which takes well over an hour for the P4-DPDK version of IPDK.
The text was updated successfully, but these errors were encountered:
Currently, the IPDK build (in particular, the P4-DPDK backend) builds a lot of dependent packages:
Ideally, we would move to a world where each of those build targets generate their own packages, and IPDK becomes the CLI to manage IPDK container images, and any glue logic required to build the IPDK containers. In this world, we're not pulling down and building everything each and every time, which takes well over an hour for the P4-DPDK version of IPDK.
The text was updated successfully, but these errors were encountered: