From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Wisam Jaddo <wisamm@mellanox.com>,
dev@dpdk.org, thomas@monjalon.net, asafp@mellanox.com,
akozyrev@nvidia.com, akozyrev@mellanox.com,
arybchenko@solarflare.com, jackmin@mellanox.com
Subject: Re: [dpdk-dev] [PATCH 00/13] app/flow-perf: add support for new items/actions
Date: Mon, 14 Sep 2020 19:15:08 +0100 [thread overview]
Message-ID: <7e168cf4-57f3-12a2-5589-f53d784915c6@intel.com> (raw)
In-Reply-To: <20200830111544.4190-1-wisamm@mellanox.com>
On 8/30/2020 12:15 PM, Wisam Jaddo wrote:
> * Some fixes.
> * Add headers modify actions support.
> * Add flag action support.
> * Add raw-encap & raw-decap actions support.
> * Add VXLAN encap & VXLAN decap actions support.
> * Add set portmask option.
> * Add icmp and icmp6 matching items support.
> * Allow installing rte flows with different modify
> headers values and different encap data for each
> rte flow.
>
> Wisam Jaddo (13):
> app/flow-perf: fix actions mask macro usage
> doc/flow-perf: fix app sections
> app/flow-perf: start supporting user order
> app/flow-perf: add header modify actions support
> app/flow-perf: add flag action support
> app/flow-perf: fix memory leak from RSS action
> app/flow-perf: add raw encap/decap actions support
> app/flow-perf: add VXLAN encap/decap actions support
> app/flow-perf: fix source ipv4 matching
> app/flow-perf: add random mark id values
> app/flow-perf: add set port mask to options
> app/flow-perf: add icmp matching support
> app/flow-perf: allow fixed values for actions
>
Series applied to dpdk-next-net/main, thanks.
next prev parent reply other threads:[~2020-09-14 18:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-30 11:15 Wisam Jaddo
2020-08-30 11:15 ` [dpdk-dev] [PATCH 01/13] app/flow-perf: fix actions mask macro usage Wisam Jaddo
2020-08-30 11:15 ` [dpdk-dev] [PATCH 02/13] doc/flow-perf: fix app sections Wisam Jaddo
2020-08-30 11:15 ` [dpdk-dev] [PATCH 03/13] app/flow-perf: start supporting user order Wisam Jaddo
2020-08-30 11:15 ` [dpdk-dev] [PATCH 04/13] app/flow-perf: add header modify actions support Wisam Jaddo
2020-08-30 11:15 ` [dpdk-dev] [PATCH 05/13] app/flow-perf: add flag action support Wisam Jaddo
2020-08-30 11:15 ` [dpdk-dev] [PATCH 06/13] app/flow-perf: fix memory leak from RSS action Wisam Jaddo
2020-08-30 11:15 ` [dpdk-dev] [PATCH 07/13] app/flow-perf: add raw encap/decap actions support Wisam Jaddo
2020-08-30 11:15 ` [dpdk-dev] [PATCH 08/13] app/flow-perf: add VXLAN " Wisam Jaddo
2020-08-30 11:15 ` [dpdk-dev] [PATCH 09/13] app/flow-perf: fix source ipv4 matching Wisam Jaddo
2020-08-30 11:15 ` [dpdk-dev] [PATCH 10/13] app/flow-perf: add random mark id values Wisam Jaddo
2020-08-30 11:15 ` [dpdk-dev] [PATCH 11/13] app/flow-perf: add set port mask to options Wisam Jaddo
2020-08-30 11:15 ` [dpdk-dev] [PATCH 12/13] app/flow-perf: add icmp matching support Wisam Jaddo
2020-08-30 11:15 ` [dpdk-dev] [PATCH 13/13] app/flow-perf: allow fixed values for actions Wisam Jaddo
2020-09-14 18:15 ` Ferruh Yigit [this message]
2020-09-21 21:36 ` [dpdk-dev] [PATCH 00/13] app/flow-perf: add support for new items/actions 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=7e168cf4-57f3-12a2-5589-f53d784915c6@intel.com \
--to=ferruh.yigit@intel.com \
--cc=akozyrev@mellanox.com \
--cc=akozyrev@nvidia.com \
--cc=arybchenko@solarflare.com \
--cc=asafp@mellanox.com \
--cc=dev@dpdk.org \
--cc=jackmin@mellanox.com \
--cc=thomas@monjalon.net \
--cc=wisamm@mellanox.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).