This commit introduce the API that is needed by the RegEx devices in
order to work with the RegEX lib.
During the probe of a RegEx device, the device should configure itself,
and allocate the resources it requires.
On completion of the device init, it should call the
rte_regex_dev_register in orde
This commit implements all the RegEx public API.
Signed-off-by: Ori Kam
---
lib/librte_regexdev/rte_regexdev.c | 298 +
1 file changed, 298 insertions(+)
diff --git a/lib/librte_regexdev/rte_regexdev.c
b/lib/librte_regexdev/rte_regexdev.c
index 4396bb5..72f1
This commit introduce the rte_regexdev_core.h file.
This file holds internal structures and API that are used by
the regexdev.
Signed-off-by: Ori Kam
---
lib/librte_regexdev/Makefile| 1 +
lib/librte_regexdev/meson.build | 2 +-
lib/librte_regexdev/rte_regexdev.h |
This patch set adds the RegEx class, which enables RegEx pattern
matching, both on HW/SW PMDs.
Example for applications that will benefit from this class:
* Next Generation Firewalls (NGFW)
* Deep Packet and Flow Inspection (DPI)
* Intrusion Prevention Systems (IPS)
* DDoS Mitigation
* Network Mon
From: Jerin Jacob
As RegEx usage become more used by DPDK applications, for example:
* Next Generation Firewalls (NGFW)
* Deep Packet and Flow Inspection (DPI)
* Intrusion Prevention Systems (IPS)
* DDoS Mitigation
* Network Monitoring
* Data Loss Prevention (DLP)
* Smart NICs
* Grammar based con
Hi Xiao,
Is the proto_id part of the basic header or not?
>From the spec it looks like a different header.
If it is part of the original header then all documentations and rte_structs
should be
changed, to reflect this.
It will be very helpful if the patch message would explain the bug and why
On 02/26, taox@intel.com wrote:
>From: Zhu Tao
>
>Setting LINK UP or LINK DOWN is divided into two parts, with
>the main task done in a separate thread, which can take up
>to 9 seconds. If cancel the thread in execution, may cause state
>inconsistencies. Therefore, must wait for the previous s
27/03/2020 15:44, Andrew Rybchenko:
> On 3/27/20 5:29 PM, Tom Barbette wrote:
> > Hi all,
> >
> > It seems rte_flow_item_eth takes its ethertype in host byte order with
> > i40e, but in network byte order with mlx5.
>
> If so, it is definitely bug in i40e, since struct rte_flow_item_eth
> defines
Hello Ruifeng,
On Mon, Mar 23, 2020 at 4:50 PM Ruifeng Wang wrote:
> > First time I see this error:
> > https://travis-ci.com/github/david-marchand/dpdk/jobs/301063161#L8410
> >
> > Did you encounter it?
>
> First time for me to see this as well.
> Not sure how often it will happen. Looks like cl
9 matches
Mail list logo