From: Raslan Darawsheh <rasland@mellanox.com>
To: Matan Azrad <matan@mellanox.com>,
Shahaf Shuler <shahafs@mellanox.com>,
Yongseok Koh <yskoh@mellanox.com>,
Slava Ovsiienko <viacheslavo@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/4] net/mlx5: accelerate DV flow counters mangement
Date: Wed, 17 Jul 2019 06:50:01 +0000 [thread overview]
Message-ID: <DB3PR0502MB3964C527FE5FEC342EEE2CCEC2C90@DB3PR0502MB3964.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1563287696-10509-1-git-send-email-matan@mellanox.com>
Hi,
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Matan Azrad
> Sent: Tuesday, July 16, 2019 5:35 PM
> To: Shahaf Shuler <shahafs@mellanox.com>; Yongseok Koh
> <yskoh@mellanox.com>; Slava Ovsiienko <viacheslavo@mellanox.com>
> Cc: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH 0/4] net/mlx5: accelerate DV flow counters
> mangement
>
> New features in devx to query and allocate flow counters by batch
> commands allow to accelerate flow counter create/destroy/query.
>
> v2:
> rebase.
>
> Matan Azrad (4):
> net/mlx5: accelerate DV flow counter transactions
> net/mlx5: resize a full counter container
> net/mlx5: accelerate DV flow counter query
> net/mlx5: allow basic counter management fallback
>
> doc/guides/rel_notes/release_19_08.rst | 2 +
> drivers/net/mlx5/Makefile | 7 +-
> drivers/net/mlx5/meson.build | 4 +-
> drivers/net/mlx5/mlx5.c | 102 ++++++
> drivers/net/mlx5/mlx5.h | 145 +++++++-
> drivers/net/mlx5/mlx5_devx_cmds.c | 225 +++++++++---
> drivers/net/mlx5/mlx5_ethdev.c | 85 ++++-
> drivers/net/mlx5/mlx5_flow.c | 147 ++++++++
> drivers/net/mlx5/mlx5_flow.h | 27 +-
> drivers/net/mlx5/mlx5_flow_dv.c | 616
> ++++++++++++++++++++++++++++++---
> drivers/net/mlx5/mlx5_flow_verbs.c | 15 +-
> drivers/net/mlx5/mlx5_glue.c | 91 +++++
> drivers/net/mlx5/mlx5_glue.h | 20 ++
> drivers/net/mlx5/mlx5_prm.h | 116 ++++++-
> 14 files changed, 1463 insertions(+), 139 deletions(-)
>
> --
> 1.8.3.1
Series applied to next-net-mlx,
Kindest regards
Raslan Darawsheh
prev parent reply other threads:[~2019-07-17 6:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 14:07 Matan Azrad
2019-07-08 14:07 ` [dpdk-dev] [PATCH 1/4] net/mlx5: accelerate DV flow counter transactions Matan Azrad
2019-07-08 14:07 ` [dpdk-dev] [PATCH 2/4] net/mlx5: resize a full counter container Matan Azrad
2019-07-08 14:07 ` [dpdk-dev] [PATCH 3/4] net/mlx5: accelerate DV flow counter query Matan Azrad
2019-07-08 14:07 ` [dpdk-dev] [PATCH 4/4] net/mlx5: allow basic counter management fallback Matan Azrad
2019-07-16 14:34 ` [dpdk-dev] [PATCH 0/4] net/mlx5: accelerate DV flow counters mangement Matan Azrad
2019-07-16 14:34 ` [dpdk-dev] [PATCH 1/4] net/mlx5: accelerate DV flow counter transactions Matan Azrad
2019-07-16 14:34 ` [dpdk-dev] [PATCH 2/4] net/mlx5: resize a full counter container Matan Azrad
2019-07-16 14:34 ` [dpdk-dev] [PATCH 3/4] net/mlx5: accelerate DV flow counter query Matan Azrad
2019-07-16 14:34 ` [dpdk-dev] [PATCH 4/4] net/mlx5: allow basic counter management fallback Matan Azrad
2019-07-17 6:50 ` Raslan Darawsheh [this message]
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=DB3PR0502MB3964C527FE5FEC342EEE2CCEC2C90@DB3PR0502MB3964.eurprd05.prod.outlook.com \
--to=rasland@mellanox.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--cc=shahafs@mellanox.com \
--cc=viacheslavo@mellanox.com \
--cc=yskoh@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).