From: Thomas Monjalon <thomas@monjalon.net>
To: Gaetan Rivet <gaetan.rivet@6wind.com>
Cc: dev@dpdk.org, adrien.mazarguil@6wind.com
Subject: Re: [dpdk-dev] [PATCH v2] ethdev: add flow API rule copy function
Date: Tue, 27 Jun 2017 23:48:34 +0200 [thread overview]
Message-ID: <74944501.qiFWTKhjmz@xps> (raw)
In-Reply-To: <c3dbfe0bda1da236f10023f379329e985281b9c2.1495207150.git.gaetan.rivet@6wind.com>
19/05/2017 17:21, Gaetan Rivet:
> --- a/lib/librte_ether/rte_flow.c
> +++ b/lib/librte_ether/rte_flow.c
> @@ -33,12 +33,70 @@
>
> #include <stdint.h>
>
> +#include <rte_common.h>
> #include <rte_errno.h>
> #include <rte_branch_prediction.h>
> #include "rte_ethdev.h"
> #include "rte_flow_driver.h"
> #include "rte_flow.h"
>
> +/** Generate flow_item[] entry. */
> +#define MK_FLOW_ITEM(t, s) \
> + [RTE_FLOW_ITEM_TYPE_ ## t] = { \
> + .name t, \
> + .size = s, \
> + }
> +
> +/** Information about known flow pattern items. */
> +const struct rte_flow_desc_data rte_flow_desc_item[] = {
> + MK_FLOW_ITEM(END, 0),
> + MK_FLOW_ITEM(VOID, 0),
> + MK_FLOW_ITEM(INVERT, 0),
> + MK_FLOW_ITEM(ANY, sizeof(struct rte_flow_item_any)),
> + MK_FLOW_ITEM(PF, 0),
> + MK_FLOW_ITEM(VF, sizeof(struct rte_flow_item_vf)),
> + MK_FLOW_ITEM(PORT, sizeof(struct rte_flow_item_port)),
> + MK_FLOW_ITEM(RAW, sizeof(struct rte_flow_item_raw)), /* +pattern[] */
> + MK_FLOW_ITEM(ETH, sizeof(struct rte_flow_item_eth)),
> + MK_FLOW_ITEM(VLAN, sizeof(struct rte_flow_item_vlan)),
> + MK_FLOW_ITEM(IPV4, sizeof(struct rte_flow_item_ipv4)),
> + MK_FLOW_ITEM(IPV6, sizeof(struct rte_flow_item_ipv6)),
> + MK_FLOW_ITEM(ICMP, sizeof(struct rte_flow_item_icmp)),
> + MK_FLOW_ITEM(UDP, sizeof(struct rte_flow_item_udp)),
> + MK_FLOW_ITEM(TCP, sizeof(struct rte_flow_item_tcp)),
> + MK_FLOW_ITEM(SCTP, sizeof(struct rte_flow_item_sctp)),
> + MK_FLOW_ITEM(VXLAN, sizeof(struct rte_flow_item_vxlan)),
> + MK_FLOW_ITEM(MPLS, sizeof(struct rte_flow_item_mpls)),
> + MK_FLOW_ITEM(GRE, sizeof(struct rte_flow_item_gre)),
> +};
When rebasing, do not forget these new lines:
+ MK_FLOW_ITEM(E_TAG, sizeof(struct rte_flow_item_e_tag)),
+ MK_FLOW_ITEM(NVGRE, sizeof(struct rte_flow_item_nvgre)),
from 0f01a7e38394 ("app/testpmd: fix creating E-Tag and NVGRE flow rules")
next prev parent reply other threads:[~2017-06-27 21:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 15:09 [dpdk-dev] [PATCH] " Gaetan Rivet
2017-05-19 15:21 ` [dpdk-dev] [PATCH v2] " Gaetan Rivet
2017-06-27 21:48 ` Thomas Monjalon [this message]
2017-06-27 22:00 ` Thomas Monjalon
2017-07-06 16:56 ` [dpdk-dev] [PATCH v3] " Adrien Mazarguil
2017-07-06 17:11 ` Gaëtan Rivet
2017-07-07 0:08 ` [dpdk-dev] [PATCH v4] " Gaetan Rivet
2017-07-08 15:56 ` Thomas Monjalon
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=74944501.qiFWTKhjmz@xps \
--to=thomas@monjalon.net \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=gaetan.rivet@6wind.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).