From: Bing Zhao <bingz@mellanox.com>
To: orika@mellanox.com, john.mcnamara@intel.com,
marko.kovacevic@intel.com, thomas@monjalon.net,
ferruh.yigit@intel.com, arybchenko@solarflare.com,
olivier.matz@6wind.com
Cc: dev@dpdk.org, wenzhuo.lu@intel.com, beilei.xing@intel.com,
bernard.iremonger@intel.com
Subject: [dpdk-dev] [PATCH v3 0/2] rte_flow: introduce eCPRI item for rte_flow
Date: Thu, 2 Jul 2020 20:53:40 +0800 [thread overview]
Message-ID: <1593694422-299952-1-git-send-email-bingz@mellanox.com> (raw)
In-Reply-To: <1593672361-285288-1-git-send-email-bingz@mellanox.com>
This patch set contains two commits.
1. header definition of the ethdev API
2. testpmd support for the eCPRI flow item
Bing Zhao (2):
rte_flow: add eCPRI key fields to flow API
app/testpmd: add eCPRI in flow creation patterns
app/test-pmd/cmdline_flow.c | 143 ++++++++++++++++++++++++++++++++
doc/guides/prog_guide/rte_flow.rst | 8 ++
lib/librte_ethdev/rte_flow.c | 1 +
lib/librte_ethdev/rte_flow.h | 31 +++++++
lib/librte_net/Makefile | 1 +
lib/librte_net/meson.build | 3 +-
lib/librte_net/rte_ecpri.h | 163 +++++++++++++++++++++++++++++++++++++
lib/librte_net/rte_ether.h | 1 +
8 files changed, 350 insertions(+), 1 deletion(-)
create mode 100644 lib/librte_net/rte_ecpri.h
--
2.5.5
next prev parent reply other threads:[~2020-07-02 12:54 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-28 16:20 [dpdk-dev] [PATCH] rte_flow: add eCPRI key fields to flow API Bing Zhao
2020-07-02 6:46 ` [dpdk-dev] [PATCH v2] " Bing Zhao
2020-07-02 8:06 ` Ori Kam
2020-07-02 12:53 ` Bing Zhao [this message]
2020-07-02 12:53 ` [dpdk-dev] [PATCH v3 1/2] " Bing Zhao
2020-07-05 11:34 ` Ori Kam
2020-07-02 12:53 ` [dpdk-dev] [PATCH v3 2/2] app/testpmd: add eCPRI in flow creation patterns Bing Zhao
2020-07-05 11:36 ` Ori Kam
2020-07-07 15:36 ` [dpdk-dev] [PATCH v4 0/2] rte_flow: introduce eCPRI item for rte_flow Bing Zhao
2020-07-07 15:36 ` [dpdk-dev] [PATCH v4 1/2] rte_flow: add eCPRI key fields to flow API Bing Zhao
2020-07-08 18:49 ` Akhil Goyal
2020-07-09 3:58 ` Bing Zhao
2020-07-07 15:36 ` [dpdk-dev] [PATCH v4 2/2] app/testpmd: add eCPRI in flow creation patterns Bing Zhao
2020-07-10 8:45 ` [dpdk-dev] [PATCH v5 0/2] rte_flow: introduce eCPRI item for rte_flow Bing Zhao
2020-07-10 8:45 ` [dpdk-dev] [PATCH v5 1/2] rte_flow: add eCPRI key fields to flow API Bing Zhao
2020-07-10 14:31 ` Olivier Matz
2020-07-11 4:25 ` Bing Zhao
2020-07-12 13:17 ` Olivier Matz
2020-07-12 14:28 ` Bing Zhao
2020-07-12 14:43 ` Olivier Matz
2020-07-10 8:45 ` [dpdk-dev] [PATCH v5 2/2] app/testpmd: add eCPRI in flow creation patterns Bing Zhao
2020-07-12 13:35 ` [dpdk-dev] [PATCH v6 0/2] rte_flow: introduce eCPRI item for rte_flow Bing Zhao
2020-07-12 13:35 ` [dpdk-dev] [PATCH v6 1/2] rte_flow: add eCPRI key fields to flow API Bing Zhao
2020-07-12 14:45 ` Olivier Matz
2020-07-12 14:50 ` Bing Zhao
2020-07-13 0:50 ` Thomas Monjalon
2020-07-13 8:30 ` Ferruh Yigit
2020-07-12 13:35 ` [dpdk-dev] [PATCH v6 2/2] app/testpmd: add eCPRI in flow creation patterns Bing Zhao
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=1593694422-299952-1-git-send-email-bingz@mellanox.com \
--to=bingz@mellanox.com \
--cc=arybchenko@solarflare.com \
--cc=beilei.xing@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=olivier.matz@6wind.com \
--cc=orika@mellanox.com \
--cc=thomas@monjalon.net \
--cc=wenzhuo.lu@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).