dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Beilei Xing <beilei.xing@intel.com>, jingjing.wu@intel.com
Cc: dev@dpdk.org
Subject: Re: [PATCH v2 1/4] net/i40e: support flexible payload parsing for FDIR
Date: Thu, 8 Jun 2017 11:02:34 +0100	[thread overview]
Message-ID: <9ac3dc45-94a6-bba5-4a34-3c94c7d80d73@intel.com> (raw)
In-Reply-To: <1496822996-26398-2-git-send-email-beilei.xing@intel.com>

On 6/7/2017 9:09 AM, Beilei Xing wrote:
> This patch adds flexible payload parsing support for
> flow director filter.
> 
> Signed-off-by: Beilei Xing <beilei.xing@intel.com>

<...>

>  /* 1. Last in item should be NULL as range is not supported.
> - * 2. Supported flow type and input set: refer to array
> + * 2. Supported patterns: refer to array i40e_supported_patterns.
> + * 3. Supported flow type and input set: refer to array
>   *    default_inset_table in i40e_ethdev.c.
> - * 3. Mask of fields which need to be matched should be
> + * 4. Mask of fields which need to be matched should be
>   *    filled with 1.
> - * 4. Mask of fields which needn't to be matched should be
> + * 5. Mask of fields which needn't to be matched should be
>   *    filled with 0.
>   */
>  static int
> @@ -769,15 +948,29 @@ i40e_flow_parse_fdir_pattern(struct rte_eth_dev *dev,
>  	const struct rte_flow_item_tcp *tcp_spec, *tcp_mask;
>  	const struct rte_flow_item_udp *udp_spec, *udp_mask;
>  	const struct rte_flow_item_sctp *sctp_spec, *sctp_mask;
> +	const struct rte_flow_item_raw *raw_spec, *raw_mask;
>  	const struct rte_flow_item_vf *vf_spec;
> +
>  	uint32_t flow_type = RTE_ETH_FLOW_UNKNOWN;
>  	enum i40e_filter_pctype pctype;
>  	uint64_t input_set = I40E_INSET_NONE;
>  	uint16_t flag_offset;
>  	enum rte_flow_item_type item_type;
>  	enum rte_flow_item_type l3 = RTE_FLOW_ITEM_TYPE_END;
> -	uint32_t j;
> +	uint32_t i, j;
> +	enum i40e_flxpld_layer_idx layer_idx = I40E_FLXPLD_L2_IDX;
> +	uint8_t raw_id = 0;
> +	struct rte_flow_item_raw raw_arr[I40E_MAX_FLXPLD_FIED];

Hi Beilei,

Getting build error [1] with ICC, can you please check?


[1]
...dpdk/drivers/net/i40e/i40e_flow.c(2302):
error #2405: array of elements containing a flexible array member is
nonstandard
        struct rte_flow_item_raw raw_arr[I40E_MAX_FLXPLD_FIED];
                                 ^

  parent reply	other threads:[~2017-06-08 10:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-24  6:10 [PATCH 0/3] net/i40e: add advanced features for FDIR Beilei Xing
2017-05-24  6:10 ` [PATCH 1/3] net/i40e: support flexible payload parsing " Beilei Xing
2017-06-06  7:46   ` Lu, Wenzhuo
2017-06-06  7:58     ` Xing, Beilei
2017-05-24  6:10 ` [PATCH 2/3] net/i40e: support input set selection " Beilei Xing
2017-06-06  8:04   ` Lu, Wenzhuo
2017-05-24  6:10 ` [PATCH 3/3] net/i40e: update supported patterns " Beilei Xing
2017-06-06  8:32   ` Lu, Wenzhuo
2017-06-07  8:09 ` [PATCH v2 0/4] net/i40e: add advanced features " Beilei Xing
2017-06-07  8:09   ` [PATCH v2 1/4] net/i40e: support flexible payload parsing " Beilei Xing
2017-06-08  2:48     ` Lu, Wenzhuo
2017-06-08 10:02     ` Ferruh Yigit [this message]
2017-06-07  8:09   ` [PATCH v2 2/4] net/i40e: support input set selection " Beilei Xing
2017-06-07  8:09   ` [PATCH v2 3/4] net/i40e: update supported patterns " Beilei Xing
2017-06-07  8:09   ` [PATCH v2 4/4] net/i40e: support ether pattern " Beilei Xing
2017-06-08  2:59     ` Lu, Wenzhuo
2017-06-09  8:21   ` [PATCH v3 0/4] net/i40e: add advanced features " Beilei Xing
2017-06-09  8:21     ` [PATCH v3 1/4] net/i40e: support flexible payload parsing " Beilei Xing
2017-06-09  8:21     ` [PATCH v3 2/4] net/i40e: support input set selection " Beilei Xing
2017-06-09  8:21     ` [PATCH v3 3/4] net/i40e: update supported patterns " Beilei Xing
2017-06-09  8:21     ` [PATCH v3 4/4] net/i40e: support ether pattern " Beilei Xing
2017-06-09 10:59     ` [PATCH v3 0/4] net/i40e: add advanced features " Ferruh Yigit

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=9ac3dc45-94a6-bba5-4a34-3c94c7d80d73@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.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;
as well as URLs for NNTP newsgroup(s).