DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Kirill Rybalchenko <kirill.rybalchenko@intel.com>, dev@dpdk.org
Cc: andrey.chilikin@intel.com, beilei.xing@intel.com, jingjing.wu@intel.com
Subject: Re: [dpdk-dev] [PATCH] net/i40e: add support for packet template to flow director
Date: Mon, 23 Oct 2017 15:11:30 -0700	[thread overview]
Message-ID: <e3219fb1-7263-8923-d285-330d0be37e93@intel.com> (raw)
In-Reply-To: <1508403636-91235-1-git-send-email-kirill.rybalchenko@intel.com>

On 10/19/2017 2:00 AM, Kirill Rybalchenko wrote:
> For complex packets use raw flow type with pre-constructed packet buffer
> instead of creating a packet internally in PMD.
> 
> Signed-off-by: Kirill Rybalchenko <kirill.rybalchenko@intel.com>

<...>

> diff --git a/drivers/net/i40e/rte_pmd_i40e.h b/drivers/net/i40e/rte_pmd_i40e.h
> index 467b415..fd744af 100644
> --- a/drivers/net/i40e/rte_pmd_i40e.h
> +++ b/drivers/net/i40e/rte_pmd_i40e.h
> @@ -250,6 +250,64 @@ struct rte_pmd_i40e_queue_regions {
>  		region[RTE_PMD_I40E_REGION_MAX_NUM];
>  };
>  
> +/* Behavior will be taken if raw packet template is matched. */
> +enum rte_pmd_i40e_pkt_template_behavior {
> +	RTE_PMD_I40E_PKT_TEMPLATE_ACCEPT = 0,

Assignment is not required, it is zero by default.

> +	RTE_PMD_I40E_PKT_TEMPLATE_REJECT,
> +	RTE_PMD_I40E_PKT_TEMPLATE_PASSTHRU,
> +};
> +
> +/* Flow director report status
> + * It defines what will be reported if raw packet template is matched.
> + */
> +enum rte_pmd_i40e_pkt_template_status {
> +	RTE_PMD_I40E_PKT_TEMPLATE_NO_REPORT_STATUS = 0,
> +	RTE_PMD_I40E_PKT_TEMPLATE_REPORT_ID,
> +	RTE_PMD_I40E_PKT_TEMPLATE_REPORT_ID_FLEX_4,
> +	RTE_PMD_I40E_PKT_TEMPLATE_REPORT_FLEX_8,
> +};
> +
> +/* A structure used to define an action when raw packet template is matched. */
> +struct rte_pmd_i40e_pkt_template_action {
> +	uint16_t rx_queue;
> +	enum rte_pmd_i40e_pkt_template_behavior behavior;
> +	enum rte_pmd_i40e_pkt_template_status report_status;
> +	uint8_t flex_off;
> +};
> +
> +/* A structure used to define the input for raw packet template. */
> +struct rte_pmd_i40e_pkt_template_input {
> +	uint16_t pctype; /* pctype used for raw packet template. */
> +	void *packet;    /* Buffer conatining raw packet template. */
> +	uint32_t length; /* Length of buffer with raw packet template. */
> +};
> +
> +struct rte_pmd_i40e_pkt_template_conf {
> +	struct rte_pmd_i40e_pkt_template_input input;
> +	struct rte_pmd_i40e_pkt_template_action action;
> +	uint32_t soft_id;
> +};

These are in public header now. Can you please document structs and elements of
them via doxygen style comments?

Thanks,
ferruh

  reply	other threads:[~2017-10-23 22:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-19  9:00 Kirill Rybalchenko
2017-10-23 22:11 ` Ferruh Yigit [this message]
2017-10-24 14:08 ` [dpdk-dev] [PATCH v2] " Kirill Rybalchenko
2017-10-24 18:02   ` Ferruh Yigit
2017-10-24 18:07     ` 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=e3219fb1-7263-8923-d285-330d0be37e93@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=andrey.chilikin@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.com \
    --cc=kirill.rybalchenko@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).