DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Suanming Mou <suanmingm@nvidia.com>,
	Slava Ovsiienko <viacheslavo@nvidia.com>,
	Matan Azrad <matan@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix shared RSS action release
Date: Mon, 9 Nov 2020 08:22:36 +0000	[thread overview]
Message-ID: <DM6PR12MB27480BCC13FB98FCD5D32372CFEA0@DM6PR12MB2748.namprd12.prod.outlook.com> (raw)
In-Reply-To: <1604632107-146708-1-git-send-email-suanmingm@nvidia.com>

> -----Original Message-----
> From: Suanming Mou <suanmingm@nvidia.com>
> Sent: Friday, November 6, 2020 5:08 AM
> To: Slava Ovsiienko <viacheslavo@nvidia.com>; Matan Azrad
> <matan@nvidia.com>
> Cc: Raslan Darawsheh <rasland@nvidia.com>; dev@dpdk.org
> Subject: [PATCH] net/mlx5: fix shared RSS action release
> As shared RSS action is global standalone action, the shared action
> should be maintained only by the shared action management functions.
> Currently, the shared RSS action hrxq uses the same fate action type
> with existed general queues, and implicitly uses the deprecate refcnt
> increment to indicate the hrxq is in using which leads the hrxq be
> released when flow is destroyed.
> This commit adds a new fate action type for shared RSS action to
> handle the shared RSS action 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>
> ---
Patch applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh

  reply	other threads:[~2020-11-09  8:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-06  3:08 Suanming Mou
2020-11-09  8:22 ` Raslan Darawsheh [this message]
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

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=DM6PR12MB27480BCC13FB98FCD5D32372CFEA0@DM6PR12MB2748.namprd12.prod.outlook.com \
    --to=rasland@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@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).