68b95704a6
Previously, the pipeline build operation was done based on the specification file (typically produced by the P4 compiler), then the C code with optimized functions for the pipeline actions and instructions was generated, built into a shared object library, loaded and installed into the pipeline in a completely hardcoded and non-customizable way. Now, this process is split into three explicit stages: i) code generation (specification file -> C file); ii) code build (C file -> shared object library); iii) code installation (library load into the pipeline). Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com> Signed-off-by: Kamalakannan R <kamalakannan.r@intel.com> |
||
---|---|---|
.. | ||
meson.build | ||
rte_pipeline.c | ||
rte_pipeline.h | ||
rte_port_in_action.c | ||
rte_port_in_action.h | ||
rte_swx_ctl.c | ||
rte_swx_ctl.h | ||
rte_swx_extern.h | ||
rte_swx_pipeline_internal.h | ||
rte_swx_pipeline_spec.c | ||
rte_swx_pipeline_spec.h | ||
rte_swx_pipeline.c | ||
rte_swx_pipeline.h | ||
rte_table_action.c | ||
rte_table_action.h | ||
version.map |