public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Lukas Sismis <sismis@dyna-nic.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH v8 3/6] flow_parser: add shared parser library
Date: Thu, 29 Jan 2026 09:28:15 -0800	[thread overview]
Message-ID: <20260129092815.750af8c6@phoenix.local> (raw)
In-Reply-To: <20260129114202.61185-4-sismis@dyna-nic.com>

On Thu, 29 Jan 2026 12:41:59 +0100
Lukas Sismis <sismis@dyna-nic.com> wrote:

> +
> +struct rte_flow_parser_ctx {
> +	struct rte_flow_parser_vxlan_encap_conf vxlan_encap_conf;
> +	struct rte_flow_parser_nvgre_encap_conf nvgre_encap_conf;
> +	struct rte_flow_parser_l2_encap_conf l2_encap_conf;
> +	struct rte_flow_parser_l2_decap_conf l2_decap_conf;
> +	struct rte_flow_parser_mplsogre_encap_conf mplsogre_encap_conf;
> +	struct rte_flow_parser_mplsogre_decap_conf mplsogre_decap_conf;
> +	struct rte_flow_parser_mplsoudp_encap_conf mplsoudp_encap_conf;
> +	struct rte_flow_parser_mplsoudp_decap_conf mplsoudp_decap_conf;
> +	struct rte_flow_action_conntrack conntrack_context;
> +	struct raw_encap_conf raw_encap_confs[RAW_ENCAP_CONFS_MAX_NUM];
> +	struct raw_decap_conf raw_decap_confs[RAW_ENCAP_CONFS_MAX_NUM];
> +	struct ipv6_ext_push_conf ipv6_ext_push_confs[IPV6_EXT_PUSH_CONFS_MAX_NUM];
> +	struct ipv6_ext_remove_conf ipv6_ext_remove_confs[IPV6_EXT_PUSH_CONFS_MAX_NUM];
> +	struct rte_flow_action_raw_encap raw_encap_conf_cache[RAW_ENCAP_CONFS_MAX_NUM];
> +	struct rte_flow_action_raw_decap raw_decap_conf_cache[RAW_ENCAP_CONFS_MAX_NUM];
> +	struct rte_flow_action_ipv6_ext_push
> +		ipv6_ext_push_action_cache[IPV6_EXT_PUSH_CONFS_MAX_NUM];
> +	struct rte_flow_action_ipv6_ext_remove
> +		ipv6_ext_remove_action_cache[IPV6_EXT_PUSH_CONFS_MAX_NUM];
> +	struct raw_sample_conf raw_sample_confs[RAW_SAMPLE_CONFS_MAX_NUM];
> +	struct rte_flow_action_mark sample_mark[RAW_SAMPLE_CONFS_MAX_NUM];
> +	struct rte_flow_action_queue sample_queue[RAW_SAMPLE_CONFS_MAX_NUM];
> +	struct rte_flow_action_count sample_count[RAW_SAMPLE_CONFS_MAX_NUM];
> +	struct rte_flow_action_port_id sample_port_id[RAW_SAMPLE_CONFS_MAX_NUM];
> +	struct rte_flow_action_raw_encap sample_encap[RAW_SAMPLE_CONFS_MAX_NUM];
> +	struct action_vxlan_encap_data sample_vxlan_encap[RAW_SAMPLE_CONFS_MAX_NUM];
> +	struct action_nvgre_encap_data sample_nvgre_encap[RAW_SAMPLE_CONFS_MAX_NUM];
> +	struct action_rss_data sample_rss_data[RAW_SAMPLE_CONFS_MAX_NUM];
> +	struct rte_flow_action_vf sample_vf[RAW_SAMPLE_CONFS_MAX_NUM];
> +	struct rte_flow_action_ethdev sample_port_representor[RAW_SAMPLE_CONFS_MAX_NUM];
> +	struct rte_flow_action_ethdev sample_represented_port[RAW_SAMPLE_CONFS_MAX_NUM];
> +};

How big is this beast?

  parent reply	other threads:[~2026-01-29 17:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-29 11:41 [PATCH v8 0/6] flow_parser: add shared parser library Lukas Sismis
2026-01-29 11:41 ` [PATCH v8 1/6] cmdline: include stddef.h for MSVC compatibility Lukas Sismis
2026-01-29 11:43   ` Bruce Richardson
2026-01-29 11:41 ` [PATCH v8 2/6] ethdev: add RSS type helper APIs Lukas Sismis
2026-01-29 11:42 ` [PATCH v8 4/6] app/testpmd: use shared flow parser library Lukas Sismis
2026-01-29 11:42 ` [PATCH v8 5/6] examples/flow_parsing: add flow parser demo Lukas Sismis
2026-01-29 11:42 ` [PATCH v8 6/6] test: add flow parser library functional tests Lukas Sismis
     [not found] ` <20260129114202.61185-4-sismis@dyna-nic.com>
2026-01-29 17:23   ` [PATCH v8 3/6] flow_parser: add shared parser library Stephen Hemminger
2026-01-29 17:28   ` Stephen Hemminger [this message]
2026-01-30 12:13     ` Lukáš Šišmiš
2026-01-31 21:24   ` Stephen Hemminger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260129092815.750af8c6@phoenix.local \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=sismis@dyna-nic.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox