From: Dekel Peled <dekelp@nvidia.com>
To: orika@mellanox.com, thomas@monjalon.net, ferruh.yigit@intel.com,
arybchenko@solarflare.com
Cc: dev@dpdk.org, matan@nvidia.com
Subject: [dpdk-dev] [PATCH v2 0/2] ethdev: RSS expand code fix and relocate
Date: Thu, 24 Sep 2020 17:52:12 +0300 [thread overview]
Message-ID: <cover.1600958661.git.dekelp@nvidia.com> (raw)
In-Reply-To: <c1c305615ed5d286a885b554c8c821f0adffacef.1595854661.git.dekelp@mellanox.com>
Patch [1] added support for RSS flow expansion.
It was added in ethdev for public use, but until now it is used only
by MLX5 PMD.
This patch series fixes an issue in this code, removes it from ethdev
and moves it to MLX5 PMD file (following maintainer comments on v1).
[1] commit 4ed05fcd441b ("ethdev: add flow API to expand RSS flows")
---
v2: relocate code from ethdev to MLX5 PMD
---
Dekel Peled (2):
ethdev: fix RSS flow expansion in case of mismatch
ethdev: move RSS expand code from ethdev to MLX5 PMD
drivers/net/mlx5/mlx5_flow.c | 415 +++++++++++++++++++++++++++----
lib/librte_ethdev/rte_ethdev_version.map | 1 -
lib/librte_ethdev/rte_flow.c | 262 -------------------
lib/librte_ethdev/rte_flow_driver.h | 62 -----
4 files changed, 370 insertions(+), 370 deletions(-)
--
1.8.3.1
next prev parent reply other threads:[~2020-09-24 14:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 12:57 [dpdk-dev] [PATCH] ethdev: fix RSS flow expansion in case of mismatch Dekel Peled
2020-07-27 13:25 ` Dekel Peled
2020-07-27 16:21 ` Ori Kam
2020-07-28 9:14 ` Dekel Peled
2020-08-17 8:16 ` Ori Kam
2020-09-02 17:09 ` Ferruh Yigit
2020-09-24 14:52 ` Dekel Peled [this message]
2020-09-24 14:52 ` [dpdk-dev] [PATCH v2 1/2] " Dekel Peled
2020-09-24 14:52 ` [dpdk-dev] [PATCH v2 2/2] ethdev: move RSS expand code from ethdev to MLX5 PMD Dekel Peled
2020-10-05 17:12 ` Ferruh Yigit
2020-10-05 17:13 ` [dpdk-dev] [PATCH v2 0/2] ethdev: RSS expand code fix and relocate 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=cover.1600958661.git.dekelp@nvidia.com \
--to=dekelp@nvidia.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=matan@nvidia.com \
--cc=orika@mellanox.com \
--cc=thomas@monjalon.net \
/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).