nfp: flower: refactor function "is_post_ct_flow"
authorWentao Jia <wentao.jia@corigine.com>
Tue, 14 Mar 2023 06:36:07 +0000 (08:36 +0200)
committerJakub Kicinski <kuba@kernel.org>
Thu, 16 Mar 2023 05:16:22 +0000 (22:16 -0700)
commit0b8d953cce26287a7f5eb78ff49496e9836c88ed
treed66f9f893bc0c2d46a5f0edc5c46a3785813fad3
parentcee7b339d806f71df611087724ddfbaad2d8f8b7
nfp: flower: refactor function "is_post_ct_flow"

'ct_clear' action only or no ct action is supported for 'post_ct_flow'.
But in scenario of multiple ct zones, one non 'ct_clear' ct action or
more ct actions, including 'ct_clear action', may be present in one flow
rule. If ct state match key is 'ct_established', the flow rule is still
expected to be classified as 'post_ct_flow'. Check ct status first in
function "is_post_ct_flow" to achieve this.

Signed-off-by: Wentao Jia <wentao.jia@corigine.com>
Acked-by: Simon Horman <simon.horman@corigine.com>
Signed-off-by: Louis Peens <louis.peens@corigine.com>
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
drivers/net/ethernet/netronome/nfp/flower/conntrack.c