Not all PMDs allow RTE flow rules to be created before start.
This capability will be set for the ones that allow it.
Signed-off-by: Martin Havlik
---
lib/ethdev/rte_ethdev.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/lib/ethdev/rte_ethdev.h b/lib/ethdev/rte_ethdev.h
index bef24173cf
The flow rule governing dedicated queues is now created
when the slave allows it. That is before or after the start
of the slave device, as the PMD is able to.
Signed-off-by: Martin Havlik
---
drivers/net/bonding/rte_eth_bond_pmd.c | 25 +++--
1 file changed, 19 insertions
all appropriate PMDs
in `rte_eth_dev_info->dev_capa`.
That is not pretty, but it holds the semantics of a capability
correctly, as opposed to making it a requirement to have the device
started before creating flow rules.
[1] https://www.mail-archive.com/dev@dpdk.org/msg214840.html
Martin Havlik
In bonding mode 4 (8023ad), dedicated queues are not working
on mlx5 NICs.
Signed-off-by: Martin Havlik
---
doc/guides/testpmd_app_ug/testpmd_funcs.rst | 3 +++
1 file changed, 3 insertions(+)
diff --git a/doc/guides/testpmd_app_ug/testpmd_funcs.rst
b/doc/guides/testpmd_app_ug
Included info on dedicated queues and added related
note about issue on mlx5.
Signed-off-by: Martin Havlik
---
doc/guides/prog_guide/link_bonding_poll_mode_drv_lib.rst | 8
1 file changed, 8 insertions(+)
diff --git a/doc/guides/prog_guide/link_bonding_poll_mode_drv_lib.rst
b/doc
The ability to create RTE flow rules, depending on
port status, can and does differ between PMDs.
Now the doc reflects that.
Signed-off-by: Martin Havlik
---
doc/guides/prog_guide/rte_flow.rst | 4
1 file changed, 4 insertions(+)
diff --git a/doc/guides/prog_guide/rte_flow.rst
b/doc
It is now clearly stated that RTE flow rules can be
created only after the port is started.
Signed-off-by: Martin Havlik
---
doc/guides/nics/mlx5.rst | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
index f5b727c1ee
t;Min Hu (Connor)"
Martin Havlik (4):
doc: clarify RTE flow behaviour on port stop/start
doc: specify RTE flow create behaviour
doc: update bonding mode 8023ad info
doc: note that testpmd on mlx5 has dedicated queues problem
doc/guides/nics/mlx5.rst |
When dedicated queues are enabled, mlx5 PMD fails to install RTE Flows
if the underlying ethdev is not started:
bond_ethdev_8023ad_flow_set(267) - bond_ethdev_8023ad_flow_set: port not
started (slave_port=0 queue_id=1)
Signed-off-by: Martin Havlik
Cc: Jan Viktorin
---
drivers/net/bonding
Return value from bond_ethdev_8023ad_flow_set() is now checked
and appropriate message is logged on error.
Fixes: 112891cd27e5 ("net/bonding: add dedicated HW queues for LACP control")
Cc: tomaszx.kula...@intel.com
Signed-off-by: Martin Havlik
Cc: Jan Viktorin
---
drivers/n
Return value is now saved to errval and log message on error
reports correct function name, doesn't use q_id which was out of context,
and uses up-to-date errval.
Fixes: 112891cd27e5 ("net/bonding: add dedicated HW queues for LACP control")
Cc: tomaszx.kula...@intel.com
Signed
oherty
Cc: Tomasz Kulasek
Cc: Jan Viktorin
Martin Havlik (3):
net/bonding: fix proper return value check and correct log message
net/bonding: fix not checked return value
net/bonding: start ethdev prior to setting 8023ad flow
drivers/net/bonding/rte_eth_bond_
12 matches
Mail list logo
