Add support for matching random value using the "rte_flow_item_random"
structure.
Depends-on: series-30553 ("ethdev: add random item support")
v2:
- Rebase.
- Move release notes to the new release file.
v3:
- Fix typos in commit message and release notes.
- Update limitations.
v4:
- Fix us
From: Erez Shitrit
The HW adds a random number per each hash, this value can be used for
statistic calculation over the packets, for example by setting one bit in
the mask of that field we will get half of the traffic in the flow, and
so on with the rest of the mask.
Signed-off-by: Erez Shitrit
Add support for random item in HWS mode.
Signed-off-by: Michael Baum
Acked-by: Dariusz Sosnowski
---
doc/guides/nics/features/mlx5.ini | 1 +
doc/guides/nics/mlx5.rst | 9 +
doc/guides/rel_notes/release_24_03.rst | 3 +++
drivers/net/mlx5/mlx5_flow_dv.c| 5 +++
Add support to use "RTE_FLOW_ITEM_TYPE_COMPARE" with
"RTE_FLOW_FIELD_RAMDOM" as an argument.
The random field is supported only when base is an immediate value,
random field cannot be compared with enother field.
Signed-off-by: Michael Baum
---
drivers/net/mlx5/mlx5_flow_hw.c | 70 ++
Add support for compare item with "RTE_FLOW_FIELD_RANDOM".
Depends-on: series-30553 ("ethdev: add random item support")
Depends-on: series-30606 ("ethdev: add RTE_FLOW_ITEM_TYPE_COMPARE")
Depends-on: series-30665 ("net/mlx5: add random item support")
Hamdan Igbaria (1):
net/mlx5/hws: add suppor
From: Hamdan Igbaria
Add support for compare matcher, this matcher will allow
direct comparison between two packet fields, or a packet
field and a value, with fully masked DW.
For now this matcher hash table is limited to size 1x1,
thus it supports only 1 rule STE.
Signed-off-by: Hamdan Igbaria
This patch series try to enhance the bond framework to support the
offload feature better:
* Add new API to make the member port can access some information of the
bond port which belongs.
* Add new API to get the result of whether bond port is created by the
member port.
* Add two command line
From: Long Wu
Bonding PMD does not let member ports know the bonding port's
information, like how many member ports the bonding port has,
what mode the bonding port is in and so on.
Add the notification interface for bonding port to let member
port know it is added to a bonding port and what the
From: Long Wu
After bonding port notification, member port firmware may create the
bonding port. We want to get the result of creatition, so we add this
API to do the getting action.
Signed-off-by: Long Wu
Reviewed-by: Chaoyong He
Reviewed-by: James Hershaw
Reviewed-by: Peng Zhang
---
drive
From: Long Wu
Include the following new arguments for bonding ports:
- "notify_member" to enable/disable member notification.
- "dedicated_queue" to enable/disable dedicated queue.
Add these two arguments in initial argument.
Signed-off-by: Long Wu
Reviewed-by: Chaoyong He
Reviewed-by: James
From: Long Wu
Several ports may share the same PCI address, like NFP representor port.
So users cannot add this type of ports to bonding port by "--vdev"
argument in dpdk-testpmd. But the port's data name is unique between
them, include an option to add such ports to the bonding port.
After addi
From: Long Wu
Add API to support checking if the port id is a bonding
port id.
Signed-off-by: Long Wu
Reviewed-by: Chaoyong He
Reviewed-by: James Hershaw
Reviewed-by: Peng Zhang
---
drivers/net/bonding/rte_eth_bond.h | 13 +
drivers/net/bonding/rte_eth_bond_api.c | 7 ++
From: Long Wu
Add some commands to support bonding port notification in
dpdk-testpmd.
1. Users can enable the notification by command:
"set bonding notify_member (port_id) (enable|disable)"
2. If member port firmware try to create the bonding port after
notification users can get the status by
From: Long Wu
Move the flow code to a new head file to make flow related
code more clean and make the code architecture more reasonable
in the future. There is no functional change, just moving
verbatim code around.
Signed-off-by: Long Wu
Reviewed-by: James Hershaw
Reviewed-by: Chaoyong He
Re
From: Long Wu
Firmware supports several features and bond firmware creation is one
of the features. Driver notifies firmware that driver supports bond
firmware creation feature by CPP bus write. If write successfully,
initialize driver configuration.
Signed-off-by: Long Wu
Reviewed-by: Peng Zha
From: Long Wu
Driver sends control message to reset the bond firmware
configuration in flower NIC initialization. Firmware should
reset bond configuration to avoid strange problems caused
by residues.
Signed-off-by: Long Wu
Reviewed-by: Peng Zhang
Reviewed-by: Chaoyong He
---
drivers/net/nfp
From: Long Wu
If NFP physical representor port is a member port of bonding port,
its link status changed and firmware has created the bonding port,
driver will record the link status and send control message to notify
firmware.
Signed-off-by: Long Wu
Reviewed-by: Peng Zhang
Reviewed-by: Chaoyo
From: Long Wu
A NFP representor port can receive a bond notification. Then driver
will parse this notification into one of these two events:
1. Bonding port configuration may have changed.
This includes creation of a bonding port, removal/addition of
a member port, changing the bond mode, etc.
2.
From: Long Wu
Firmware sends bond firmware creation packets to driver,
driver needs to handle it in ctrl VNIC service.
Signed-off-by: Long Wu
Reviewed-by: Peng Zhang
Reviewed-by: Chaoyong He
---
drivers/net/nfp/flower/nfp_flower_bond.c | 53
drivers/net/nfp/flower/nfp_flower_bo
From: Long Wu
After bonding port notification and firmware created
the bonding port, NFP rte_flow rule adds support for
destination port to bonding port.
Signed-off-by: Long Wu
Reviewed-by: Peng Zhang
Reviewed-by: Chaoyong He
---
drivers/net/nfp/flower/nfp_flower_bond.c | 22 +++
drivers/ne
From: Long Wu
Support getting the status that whether the bonding port
is created by the nfp firmware.
Signed-off-by: Long Wu
Reviewed-by: Peng Zhang
Reviewed-by: Chaoyong He
---
drivers/net/nfp/flower/nfp_flower_bond.c | 27 +++
drivers/net/nfp/flower/nfp_flower_bond.h
On 2023/12/23 1:42 AM, Stephen Hemminger wrote:
On Fri, 22 Dec 2023 09:11:45 -0800
Stephen Hemminger wrote:
- RTE_LOG(INFO, PMD,
- "Closing ARMv8 crypto device %s on numa socket %u\n",
+ ARVM8_CRYTPO_LOG_INFO(
+ "Closing ARMv8 crypto device %s on numa soc
This patch series try to enhance the bond framework to support the
offload feature better:
* Add new API to make the member port can access some information of the
bond port which belongs.
* Add new API to get the result of whether bond port is created by the
member port.
* Add two command line
From: Long Wu
Bonding PMD does not let member ports know the bonding port's
information, like how many member ports the bonding port has,
what mode the bonding port is in and so on.
Add the notification interface for bonding port to let member
port know it is added to a bonding port and what the
From: Long Wu
After bonding port notification, member port firmware may create the
bonding port. We want to get the result of creatition, so we add this
API to do the getting action.
Signed-off-by: Long Wu
Reviewed-by: Chaoyong He
Reviewed-by: James Hershaw
Reviewed-by: Peng Zhang
---
drive
From: Long Wu
Include the following new arguments for bonding ports:
- "notify_member" to enable/disable member notification.
- "dedicated_queue" to enable/disable dedicated queue.
Add these two arguments in initial argument.
Signed-off-by: Long Wu
Reviewed-by: Chaoyong He
Reviewed-by: James
From: Long Wu
Several ports may share the same PCI address, like NFP representor port.
So users cannot add this type of ports to bonding port by "--vdev"
argument in dpdk-testpmd. But the port's data name is unique between
them, include an option to add such ports to the bonding port.
After addi
From: Long Wu
Add API to support checking if the port id is a bonding
port id.
Signed-off-by: Long Wu
Reviewed-by: Chaoyong He
Reviewed-by: James Hershaw
Reviewed-by: Peng Zhang
---
drivers/net/bonding/rte_eth_bond.h | 13 +
drivers/net/bonding/rte_eth_bond_api.c | 7 ++
From: Long Wu
Add some commands to support bonding port notification in
dpdk-testpmd.
1. Users can enable the notification by command:
"set bonding notify_member (port_id) (enable|disable)"
2. If member port firmware try to create the bonding port after
notification users can get the status by
From: Long Wu
Move the flow code to a new head file to make flow related
code more clean and make the code architecture more reasonable
in the future. There is no functional change, just moving
verbatim code around.
Signed-off-by: Long Wu
Reviewed-by: James Hershaw
Reviewed-by: Chaoyong He
Re
From: Long Wu
Driver sends control message to reset the bond firmware
configuration in flower NIC initialization. Firmware should
reset bond configuration to avoid strange problems caused
by residues.
Signed-off-by: Long Wu
Reviewed-by: Peng Zhang
Reviewed-by: Chaoyong He
---
drivers/net/nfp
From: Long Wu
Firmware supports several features and bond firmware creation is one
of the features. Driver notifies firmware that driver supports bond
firmware creation feature by CPP bus write. If write successfully,
initialize driver configuration.
Signed-off-by: Long Wu
Reviewed-by: Peng Zha
From: Long Wu
If NFP physical representor port is a member port of bonding port,
its link status changed and firmware has created the bonding port,
driver will record the link status and send control message to notify
firmware.
Signed-off-by: Long Wu
Reviewed-by: Peng Zhang
Reviewed-by: Chaoyo
From: Long Wu
A NFP representor port can receive a bond notification. Then driver
will parse this notification into one of these two events:
1. Bonding port configuration may have changed.
This includes creation of a bonding port, removal/addition of
a member port, changing the bond mode, etc.
2.
From: Long Wu
Firmware sends bond firmware creation packets to driver,
driver needs to handle it in ctrl VNIC service.
Signed-off-by: Long Wu
Reviewed-by: Peng Zhang
Reviewed-by: Chaoyong He
---
drivers/net/nfp/flower/nfp_flower_bond.c | 53
drivers/net/nfp/flower/nfp_flower_bo
From: Long Wu
Support getting the status that whether the bonding port
is created by the nfp firmware.
Signed-off-by: Long Wu
Reviewed-by: Peng Zhang
Reviewed-by: Chaoyong He
---
drivers/net/nfp/flower/nfp_flower_bond.c | 27 +++
drivers/net/nfp/flower/nfp_flower_bond.h
From: Long Wu
After bonding port notification and firmware created
the bonding port, NFP rte_flow rule adds support for
destination port to bonding port.
Signed-off-by: Long Wu
Reviewed-by: Peng Zhang
Reviewed-by: Chaoyong He
---
drivers/net/nfp/flower/nfp_flower_bond.c | 22 +++
drivers/ne
Hello,
Consider an option to describe DTS test with testpmd and SCAPY plain text
commands.
For example:
Scenario:
- Configure UDP packet in SCAPY and a flow in testpmd.
- Send UDP packet and validate testpmd output triggered by that packet.
```yaml
phase_0:
name: CONFIGURATION
tg:
38 matches
Mail list logo
