From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Dekel Peled <dekelp@nvidia.com>,
orika@mellanox.com, thomas@monjalon.net,
arybchenko@solarflare.com
Cc: dev@dpdk.org, matan@nvidia.com
Subject: Re: [dpdk-dev] [PATCH v2 0/2] ethdev: RSS expand code fix and relocate
Date: Mon, 5 Oct 2020 18:13:37 +0100 [thread overview]
Message-ID: <1ad8965c-5a6b-2a04-5de5-b14ba9594a62@intel.com> (raw)
In-Reply-To: <cover.1600958661.git.dekelp@nvidia.com>
On 9/24/2020 3:52 PM, Dekel Peled wrote:
> 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
>
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2020-10-05 19:02 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 ` [dpdk-dev] [PATCH v2 0/2] ethdev: RSS expand code fix and relocate Dekel Peled
2020-09-24 14:52 ` [dpdk-dev] [PATCH v2 1/2] ethdev: fix RSS flow expansion in case of mismatch 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 ` Ferruh Yigit [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=1ad8965c-5a6b-2a04-5de5-b14ba9594a62@intel.com \
--to=ferruh.yigit@intel.com \
--cc=arybchenko@solarflare.com \
--cc=dekelp@nvidia.com \
--cc=dev@dpdk.org \
--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).