DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Suanming Mou <suanmingm@nvidia.com>, rasland@nvidia.com
Cc: viacheslavo@nvidia.com, matan@nvidia.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] net/mlx5: fix shared RSS action release
Date: Wed, 11 Nov 2020 12:39:40 +0000	[thread overview]
Message-ID: <f51f852f-ccb9-a157-d453-05fda8dcb322@intel.com> (raw)
In-Reply-To: <1604978882-63177-1-git-send-email-suanmingm@nvidia.com>

On 11/10/2020 3:28 AM, Suanming Mou wrote:
> As shared RSS action will be shared by multiple flows, the action
> is created as global standalone action and managed only by the
> relevant shared action management functions.
> Currently, hrxqs will be created by shared RSS action or general
> queue action. For hrxqs created by shared RSS action, they should
> also only be released with shared RSS action. It's not correct to
> release the shared RSS action hrxqs as general queue actions do
> in flow destroy.
> This commit adds a new fate action type for shared RSS action to
> handle the shared RSS action hrxq release correctly.
> Fixes: e1592b6c4dea ("net/mlx5: make Rx queue thread safe")
> Signed-off-by: Suanming Mou <suanmingm@nvidia.com>
> Acked-by: Matan Azrad <matan@nvidia.com>

Applied to dpdk-next-net/main, thanks.

      reply	other threads:[~2020-11-11 12:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-06  3:08 [dpdk-dev] [PATCH] " Suanming Mou
2020-11-09  8:22 ` Raslan Darawsheh
2020-11-09 18:16 ` Ferruh Yigit
2020-11-10  1:44   ` Suanming Mou
2020-11-10  3:28 ` [dpdk-dev] [PATCH v2] " Suanming Mou
2020-11-11 12:39   ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f51f852f-ccb9-a157-d453-05fda8dcb322@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=suanmingm@nvidia.com \
    --cc=viacheslavo@nvidia.com \


* 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).