Currently, the UP4 app expects to be programmed with the same P4Info obtained when compiling the logical pipeline. However, this one contains information that might not reflect the available hw resources, for example table size, counter size, etc. For the PFCP agent to be able to take decisions on whether to accept or not new UEs, or to optimize the counter ID allocation logic, we should support the following:
Assume the UP4 app is aways pre-provisioned with a P4Info, so a client (PFCP agent) can issue a GetForwardingPipelineConfig without doing a SetForwardingPipelineConfig
Transform P4info obtained from the logical pipeline with values that reflect table/counter size on hw realization (fabric-tna)
robertmacdavid
commented
3 years ago
Currently, the UP4 app expects to be programmed with the same P4Info obtained when compiling the logical pipeline. However, this one contains information that might not reflect the available hw resources, for example table size, counter size, etc. For the PFCP agent to be able to take decisions on whether to accept or not new UEs, or to optimize the counter ID allocation logic, we should support the following:
GetForwardingPipelineConfigwithout doing aSetForwardingPipelineConfig