Maybe that's not a problem, because ACL can handle idle
packets normally, so I can't reproduce this issue with
external test cases at the moment, but I'm just describing
what idle nomatch node has to do if it wants to implement
an effect pointing to itself:
The reason why RTE_ACL_NODE_SINGLE node
Hi,
> Hi, Konstantin
>
> To illustrate this issue, I made the following modifications to the test
> cases:
> Modify the “test_data” content of the function "test_acl.c:
> test_build_ports_range":
> delete the second test data, and leave only one test message data. This way,
> when
> the funct
Hi, Konstantin
To illustrate this issue, I made the following modifications to the test cases:
Modify the “test_data” content of the function "test_acl.c:
test_build_ports_range":
delete the second test data, and leave only one test message data. This way,
when
the function "acl_run_scalar.c: rt
Hi
> The node_array[RTE_ACL_DFA_SIZE] is assigned to
> RTE_ACL_IDLE_NODE and is used as a node of
> RTE_ACL_NODE_SINGLE type, but it is currently based
> on the implementation of idle arrays with a value of all
> 0 to point to itself, which is unsafe, if the value of the
> idle array is not 0, i
The node_array[RTE_ACL_DFA_SIZE] is assigned to
RTE_ACL_IDLE_NODE and is used as a node of
RTE_ACL_NODE_SINGLE type, but it is currently based
on the implementation of idle arrays with a value of all
0 to point to itself, which is unsafe, if the value of the
idle array is not 0, it will produce und
5 matches
Mail list logo
