d/numam-dpdk
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

doc: relate bifurcated driver and flow isolated mode

Browse Source 
The relation between the isolated mode in ethdev flow API
and bifurcated driver behaviour was not clearly explained.

It is made clear in the how-to guide that isolated mode is required
for flow bifurcation to the kernel.
On the other side, the impact of the isolated mode on a bifurcated
driver is made more explicit.

Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
Reviewed-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
Acked-by: Ori Kam <orika@nvidia.com>
This commit is contained in:
Thomas Monjalon 2022-09-14 23:30:04 +02:00 committed by Andrew Rybchenko
parent 93bffd8fa0
commit 04cf171cb3
2 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
doc/guides/howto/flow_bifurcation.rst
View File

@ -55,7 +55,8 @@ The full device is already shared with the kernel driver.
The DPDK application can setup some flow steering rules,
and let the rest go to the kernel stack.
In order to define the filters strictly with flow rules,
the :ref:`flow_isolated_mode` can be configured.
the :ref:`flow_isolated_mode` must be configured,
so there is no default rule routing traffic to userspace.
There is no specific instructions to follow.
The recommended reading is the :doc:`../prog_guide/rte_flow` guide.

4
lib/ethdev/rte_flow.h
View File

@ -4121,6 +4121,10 @@ rte_flow_query(uint16_t port_id,
*
* Isolated mode guarantees that all ingress traffic comes from defined flow
* rules only (current and future).
* When enabled with a bifurcated driver,
* non-matched packets are routed to the kernel driver interface.
* When disabled (the default),
* there may be some default rules routing traffic to the DPDK port.
*
* Besides making ingress more deterministic, it allows PMDs to safely reuse
* resources otherwise assigned to handle the remaining traffic, such as