All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dekel Peled <dekelp@mellanox.com>
To: wenzhuo.lu@intel.com, jingjing.wu@intel.com,
	bernard.iremonger@intel.com, olivier.matz@6wind.com,
	adrien.mazarguil@6wind.com, thomas@monjalon.net,
	ferruh.yigit@intel.com, arybchenko@solarflare.com
Cc: shahafs@mellanox.com, dev@dpdk.org, orika@mellanox.com
Subject: [PATCH v4 0/3] support meadata as flow rule criteria
Date: Thu, 11 Oct 2018 13:49:55 +0300	[thread overview]
Message-ID: <1539254998-8555-1-git-send-email-dekelp@mellanox.com> (raw)
In-Reply-To: <1538056677-33846-1-git-send-email-dekelp@mellanox.com>

This series implements the match-metadata feature described in [1].

[1] "[RFC v2] ethdev: support metadata as flow rule criteria"
	http://mails.dpdk.org/archives/dev/2018-August/110194.html

---	
v4:
Apply code review comments:
* Change location of metadata item in mbuf
* Update debug commands

v3:
* Add link to RFC email.
* Add cover letter subject line.

v2:
* Fix some checkpatch coding style issues (wrongly sent).
---	

Dekel Peled (3):
  ethdev: support metadata as flow rule criteria
  app/testpmd: support metadata as flow rule criteria
  app/testpmd: add Tx metadata debug commands

 app/test-pmd/cmdline.c                      | 114 ++++++++++++++++++++++++++--
 app/test-pmd/cmdline_flow.c                 |  25 ++++++
 app/test-pmd/config.c                       |   1 +
 app/test-pmd/testpmd.c                      |   5 ++
 app/test-pmd/testpmd.h                      |   2 +
 app/test-pmd/txonly.c                       |   9 +++
 doc/guides/prog_guide/rte_flow.rst          |  21 +++++
 doc/guides/testpmd_app_ug/testpmd_funcs.rst |  13 +++-
 lib/librte_ethdev/rte_ethdev.c              |   1 +
 lib/librte_ethdev/rte_ethdev.h              |   5 ++
 lib/librte_ethdev/rte_flow.c                |   1 +
 lib/librte_ethdev/rte_flow.h                |  24 ++++++
 lib/librte_mbuf/rte_mbuf.c                  |   2 +
 lib/librte_mbuf/rte_mbuf.h                  |  57 +++++++++-----
 14 files changed, 255 insertions(+), 25 deletions(-)

-- 
1.8.3.1

  parent reply	other threads:[~2018-10-11 11:05 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-16 13:33 [PATCH 1/3] ethdev: support metadata as flow rule criteria Dekel Peled
2018-09-16 13:33 ` [PATCH 2/3] app/testpmd: " Dekel Peled
2018-09-16 13:33 ` [PATCH 3/3] app/testpmd: add debug command tx_metadata set <port-id> <value> Dekel Peled
2018-09-16 14:37 ` [PATCH v2 0/3] *** SUBJECT HERE *** Dekel Peled
2018-09-27 13:57   ` [PATCH v3 0/3] support meadata as flow rule criteria Dekel Peled
2018-10-03 20:46     ` Thomas Monjalon
2018-10-11 10:49     ` Dekel Peled [this message]
2018-10-16  8:42       ` [PATCH v4 " Shahaf Shuler
2018-10-17 12:03       ` [PATCH v5 0/3] support metadata " Dekel Peled
2018-10-21 14:22         ` [PATCH v6 0/2] " Dekel Peled
2018-10-22 16:14           ` Ferruh Yigit
2018-10-21 14:22         ` [PATCH v6 1/2] ethdev: " Dekel Peled
2018-10-21 14:22         ` [PATCH v6 2/2] app/testpmd: support metadata as flow rule item Dekel Peled
2018-10-22 16:13           ` Ferruh Yigit
2018-10-17 12:03       ` [PATCH v5 1/3] ethdev: support metadata as flow rule criteria Dekel Peled
2018-10-17 14:04         ` Andrew Rybchenko
2018-10-17 12:03       ` [PATCH v5 2/3] app/testpmd: support metadata as flow rule item Dekel Peled
2018-10-18 12:26         ` Ori Kam
2018-10-21 13:49           ` Dekel Peled
2018-10-17 12:03       ` [PATCH v5 3/3] app/testpmd: add Tx metadata debug commands Dekel Peled
2018-10-18  7:56         ` Ferruh Yigit
2018-10-18  8:30           ` Dekel Peled
2018-10-11 10:49     ` [PATCH v4 1/3] ethdev: support metadata as flow rule criteria Dekel Peled
2018-10-16 14:11       ` Andrew Rybchenko
2018-10-17  5:27         ` Dekel Peled
2018-10-17  6:02           ` Andrew Rybchenko
2018-10-17  7:52             ` Dekel Peled
2018-10-11 10:49     ` [PATCH v4 2/3] app/testpmd: " Dekel Peled
2018-10-11 10:49     ` [PATCH v4 3/3] app/testpmd: add Tx metadata debug commands Dekel Peled
2018-09-27 13:57   ` [PATCH v3 1/3] ethdev: support metadata as flow rule criteria Dekel Peled
2018-10-05 13:31     ` Ferruh Yigit
2018-10-05 13:39       ` Andrew Rybchenko
2018-10-05 18:20         ` Yongseok Koh
2018-10-08 15:10         ` Dekel Peled
2018-10-09 14:46         ` Ferruh Yigit
2018-10-09 14:52           ` Andrew Rybchenko
2018-09-27 13:57   ` [PATCH v3 2/3] app/testpmd: " Dekel Peled
2018-09-27 13:57   ` [PATCH v3 3/3] app/testpmd: add debug command Tx metadata set Dekel Peled
2018-10-05 13:27     ` Ferruh Yigit
2018-09-16 14:37 ` [PATCH v2 1/3] ethdev: support metadata as flow rule criteria Dekel Peled
2018-09-18  7:55   ` Xueming(Steven) Li
2018-09-16 14:37 ` [PATCH v2 2/3] app/testpmd: " Dekel Peled
2018-09-18  8:21   ` Xueming(Steven) Li
2018-09-25 11:32     ` Dekel Peled
2018-09-16 14:37 ` [PATCH v2 3/3] app/testpmd: add debug command Tx metadata set Dekel Peled
2018-09-19  5:39   ` Xueming(Steven) Li
2018-10-05 13:19   ` Ferruh Yigit
2018-10-09 14:30     ` Dekel Peled

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=1539254998-8555-1-git-send-email-dekelp@mellanox.com \
    --to=dekelp@mellanox.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=arybchenko@solarflare.com \
    --cc=bernard.iremonger@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jingjing.wu@intel.com \
    --cc=olivier.matz@6wind.com \
    --cc=orika@mellanox.com \
    --cc=shahafs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.