DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shahaf Shuler <shahafs@mellanox.com>
To: Mordechay Haimovsky <motih@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v5 0/4] support e-switch flow count action
Date: Sun, 21 Oct 2018 08:23:14 +0000	[thread overview]
Message-ID: <DB7PR05MB4426D07862FE910521C45309C3FB0@DB7PR05MB4426.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1539887363-27858-1-git-send-email-motih@mellanox.com>

Thursday, October 18, 2018 9:29 PM, Mordechay Haimovsky:
> Subject: [PATCH v5 0/4] support e-switch flow count action
> 
> The following series of patches adds support for reading the
> mlx5 e-switch flow counters.
> 
> Moti Haimovsky (4):
>   net/mlx5: refactor TC-flow infrastructure
>   net/mlx5: tc flow to use the new infrastructure
>   net/mlx5: add flow query abstraction interface
>   net/mlx5: support e-switch flow count action
> 
>  drivers/net/mlx5/mlx5.c            |  20 +-
>  drivers/net/mlx5/mlx5.h            |   4 +-
>  drivers/net/mlx5/mlx5_flow.c       |  99 ++----
>  drivers/net/mlx5/mlx5_flow.h       |  15 +-
>  drivers/net/mlx5/mlx5_flow_dv.c    |  19 ++
>  drivers/net/mlx5/mlx5_flow_tcf.c   | 644
> +++++++++++++++++++++++++++++++++++--
>  drivers/net/mlx5/mlx5_flow_verbs.c |  87 +++++
>  7 files changed, 773 insertions(+), 115 deletions(-)

Applied to next-net-mlx, thanks. 

> 
> --
> 1.8.3.1

  reply	other threads:[~2018-10-21  8:23 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-11 13:04 [dpdk-dev] [PATCH v2 0/2] " Mordechay Haimovsky
2018-10-11 13:04 ` [dpdk-dev] [PATCH v2 1/2] net/mlx5: refactor TC-flow infrastructure Mordechay Haimovsky
2018-10-14 11:07   ` Shahaf Shuler
2018-10-11 13:04 ` [dpdk-dev] [PATCH v2 2/2] net/mlx5: support e-switch flow count action Mordechay Haimovsky
2018-10-14 11:07   ` Shahaf Shuler
2018-10-16 23:50   ` [dpdk-dev] [PATCH v3 0/2] " Mordechay Haimovsky
2018-10-16 23:50   ` [dpdk-dev] [PATCH v3 1/2] net/mlx5: refactor TC-flow infrastructure Mordechay Haimovsky
2018-10-16 23:50   ` [dpdk-dev] [PATCH v3 2/2] net/mlx5: support e-switch flow count action Mordechay Haimovsky
2018-10-17 17:24     ` [dpdk-dev] [PATCH v4 0/3] " Moti Haimovsky
2018-10-17 17:24     ` [dpdk-dev] [PATCH v4 1/3] net/mlx5: refactor TC-flow infrastructure Moti Haimovsky
2018-10-17 17:24     ` [dpdk-dev] [PATCH v4 2/3] net/mlx5: add flow query abstraction interface Moti Haimovsky
2018-10-17 17:24     ` [dpdk-dev] [PATCH v4 3/3] net/mlx5: support e-switch flow count action Moti Haimovsky
2018-10-18 18:29       ` [dpdk-dev] [PATCH v5 0/4] " Moti Haimovsky
2018-10-21  8:23         ` Shahaf Shuler [this message]
2018-10-18 18:29       ` [dpdk-dev] [PATCH v5 1/4] net/mlx5: refactor TC-flow infrastructure Moti Haimovsky
2018-10-18 18:29       ` [dpdk-dev] [PATCH v5 2/4] net/mlx5: tc flow to use the new infrastructure Moti Haimovsky
2018-10-18 18:29       ` [dpdk-dev] [PATCH v5 3/4] net/mlx5: add flow query abstraction interface Moti Haimovsky
2018-10-18 18:29       ` [dpdk-dev] [PATCH v5 4/4] net/mlx5: support e-switch flow count action Moti Haimovsky
2018-10-22  9:14         ` Ferruh Yigit
2018-10-22 20:10           ` Shahaf Shuler
2018-10-23  8:40             ` Ferruh Yigit

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=DB7PR05MB4426D07862FE910521C45309C3FB0@DB7PR05MB4426.eurprd05.prod.outlook.com \
    --to=shahafs@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=motih@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).