DPDK patches and discussions
 help / color / mirror / Atom feed
From: Andrew Rybchenko <arybchenko@solarflare.com>
To: <dev@dpdk.org>
Cc: Adrien Mazarguil <adrien.mazarguil@6wind.com>,
	Jingjing Wu <jingjing.wu@intel.com>
Subject: [dpdk-dev] [PATCH 0/2] ethdev: add GENEVE to flow API
Date: Mon, 20 Nov 2017 08:21:59 +0000	[thread overview]
Message-ID: <1511166121-743-1-git-send-email-arybchenko@solarflare.com> (raw)

enum rte_flow_item_type states that items matching protocol headers
must be stacked in the same order as the protocol layers to match.
As the result the patch changes ABI since Geneve is added just after
VXLAN (the closest protocol).

In fact as far as I can see many items do not follow the requirement
already. May be the comment/requirement should be removed and GENEVE
should be added at the end of the list. If so, should be keep it just
after VXLAN in all other places or move after ESP as well?

Roman Zhukov (2):
  ethdev: add GENEVE flow pattern item
  app/testpmd: support GENEVE pattern item in flow rules

 app/test-pmd/cmdline_flow.c                 | 31 +++++++++++++++++++++++++++++
 app/test-pmd/config.c                       |  1 +
 doc/guides/prog_guide/rte_flow.rst          | 12 +++++++++++
 doc/guides/testpmd_app_ug/testpmd_funcs.rst |  5 +++++
 lib/librte_ether/rte_flow.c                 |  1 +
 lib/librte_ether/rte_flow.h                 | 31 +++++++++++++++++++++++++++++
 6 files changed, 81 insertions(+)

-- 
2.7.4

             reply	other threads:[~2017-11-20  8:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-20  8:21 Andrew Rybchenko [this message]
2017-11-20  8:22 ` [dpdk-dev] [PATCH 1/2] ethdev: add GENEVE flow pattern item Andrew Rybchenko
2017-11-23  9:39   ` Adrien Mazarguil
2017-11-20  8:22 ` [dpdk-dev] [PATCH 2/2] app/testpmd: support GENEVE pattern item in flow rules Andrew Rybchenko
2017-11-23  9:40   ` Adrien Mazarguil
2017-11-23  9:39 ` [dpdk-dev] [PATCH 0/2] ethdev: add GENEVE to flow API Adrien Mazarguil
2017-11-23 10:07   ` Andrew Rybchenko
2017-12-01 10:43 ` [dpdk-dev] [PATCH v2 " Andrew Rybchenko
2017-12-01 10:43   ` [dpdk-dev] [PATCH v2 1/2] ethdev: add GENEVE flow pattern item Andrew Rybchenko
2017-12-04 14:03     ` Adrien Mazarguil
2017-12-07 23:52       ` Ferruh Yigit
2017-12-08 10:52         ` Adrien Mazarguil
2017-12-08 19:06         ` Ferruh Yigit
2017-12-01 10:43   ` [dpdk-dev] [PATCH v2 2/2] app/testpmd: support GENEVE pattern item in flow rules Andrew Rybchenko

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=1511166121-743-1-git-send-email-arybchenko@solarflare.com \
    --to=arybchenko@solarflare.com \
    --cc=adrien.mazarguil@6wind.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).