From: Raslan Darawsheh <rasland@nvidia.com>
To: Michael Savisko <michaelsav@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Michael Savisko <michaelsav@nvidia.com>,
Ori Kam <orika@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Asaf Penso <asafp@nvidia.com>, Matan Azrad <matan@nvidia.com>
Subject: RE: [PATCH v2 0/4] net/mlx5: implement send to kernel action
Date: Thu, 20 Oct 2022 08:25:10 +0000 [thread overview]
Message-ID: <BYAPR12MB3078D52C0A92451E60B18268CF2A9@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20221019184007.1032874-1-michaelsav@nvidia.com>
Hi,
> -----Original Message-----
> From: Michael Savisko <michaelsav@nvidia.com>
> Sent: Wednesday, October 19, 2022 9:40 PM
> To: dev@dpdk.org
> Cc: Michael Savisko <michaelsav@nvidia.com>; Ori Kam <orika@nvidia.com>;
> Slava Ovsiienko <viacheslavo@nvidia.com>; Asaf Penso
> <asafp@nvidia.com>; Matan Azrad <matan@nvidia.com>
> Subject: [PATCH v2 0/4] net/mlx5: implement send to kernel action
>
> This patchset provides mlx5 implementation of new rte_flow action
> RTE_FLOW_ACTION_TYPE_SEND_TO_KERNEL.
>
> Depends-on: patch-6838dd4bf976 ("ethdev: add send to kernel action")
>
> Signed-off-by: Michael Savisko <michaelsav@nvidia.com>
> Acked-by: Matan Azrad <matan@nvidia.com>
> ---
> v2:
> - updated after code review
>
> v1:
> https://patches.dpdk.org/project/dpdk/list/?series=24734
>
> ---
> Michael Savisko (4):
> common/mlx5: new glue callback for send to kernel action
> net/mlx5: introduce new mlx5 action flag
> net/mlx5: add send to kernel action resource holder
> net/mlx5: translation of rte flow send to kernel action
>
> doc/guides/nics/features/default.ini | 1 +
> doc/guides/nics/features/mlx5.ini | 1 +
> drivers/common/mlx5/linux/meson.build | 2 +
> drivers/common/mlx5/linux/mlx5_glue.c | 17 ++++++
> drivers/common/mlx5/linux/mlx5_glue.h | 2 +
> drivers/net/mlx5/linux/mlx5_flow_os.h | 22 ++++++++
> drivers/net/mlx5/linux/mlx5_os.c | 13 +++++
> drivers/net/mlx5/mlx5.h | 6 ++
> drivers/net/mlx5/mlx5_flow.c | 32 +++++++++++
> drivers/net/mlx5/mlx5_flow.h | 10 +++-
> drivers/net/mlx5/mlx5_flow_dv.c | 74 +++++++++++++++++++++++--
> drivers/net/mlx5/mlx5_flow_hw.c | 3 +
> drivers/net/mlx5/windows/mlx5_flow_os.h | 24 ++++++++
> 13 files changed, 200 insertions(+), 7 deletions(-)
>
> --
> 2.27.0
Series applied to next-net-mlx,
With a small fix for the missing doc on the features list,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2022-10-20 8:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 18:40 Michael Savisko
2022-10-19 18:40 ` [PATCH v2 1/4] common/mlx5: new glue callback for " Michael Savisko
2022-10-19 18:40 ` [PATCH v2 2/4] net/mlx5: introduce new mlx5 action flag Michael Savisko
2022-10-20 8:23 ` Raslan Darawsheh
2022-10-19 18:40 ` [PATCH v2 3/4] net/mlx5: add send to kernel action resource holder Michael Savisko
2022-10-19 18:40 ` [PATCH v2 4/4] net/mlx5: translation of rte flow send to kernel action Michael Savisko
2022-10-20 8:25 ` 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=BYAPR12MB3078D52C0A92451E60B18268CF2A9@BYAPR12MB3078.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=asafp@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=michaelsav@nvidia.com \
--cc=orika@nvidia.com \
--cc=viacheslavo@nvidia.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).