c40c061a02
The HW steering uses async queue-based flow rules management mechanism. The matcher and part of the actions have been prepared during flow table creation. Some remaining actions will be constructed during flow creation if needed. A flow postpone attribute bit describes if flow management should be applied to the HW directly. An extra push function is provided to force push all the cached flows to the HW. Once the flow has been applied to the HW, the pull function will be called to get the queued creation/destruction flows. The DR rule flow memory is represented in PMD layer instead of allocating from HW steering layer. While destroying the flow, the flow rule memory can only be freed after the CQE received. The HW queue job descriptor is currently introduced to convey the flow information and operation type between the flow insertion/destruction in the pull function. This commit adds the basic flow queue operation for: rte_flow_async_create(); rte_flow_async_destroy(); rte_flow_push(); rte_flow_pull(); Signed-off-by: Suanming Mou <suanmingm@nvidia.com> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com> |
||
---|---|---|
.. | ||
bbdevs | ||
compressdevs | ||
contributing | ||
cryptodevs | ||
dmadevs | ||
eventdevs | ||
faq | ||
freebsd_gsg | ||
gpus | ||
howto | ||
linux_gsg | ||
mempool | ||
nics | ||
platform | ||
prog_guide | ||
rawdevs | ||
regexdevs | ||
rel_notes | ||
sample_app_ug | ||
testpmd_app_ug | ||
tools | ||
vdpadevs | ||
windows_gsg | ||
conf.py | ||
custom.css | ||
index.rst | ||
meson.build |