patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Matan Azrad <matan@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Slava Ovsiienko <viacheslavo@nvidia.com>,
	"stable@dpdk.org" <stable@dpdk.org>, Bing Zhao <bingz@nvidia.com>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] net/mlx5: fix aging counter deallocation
Date: Wed, 9 Jun 2021 15:40:02 +0000
Message-ID: <DM4PR12MB505441C4532E48E03119FE89CF369@DM4PR12MB5054.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210609123251.3558588-1-matan@nvidia.com>

Hi,

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Matan Azrad
> Sent: Wednesday, June 9, 2021 3:33 PM
> To: dev@dpdk.org
> Cc: Slava Ovsiienko <viacheslavo@nvidia.com>; stable@dpdk.org; Bing Zhao
> <bingz@nvidia.com>
> Subject: [dpdk-dev] [PATCH] net/mlx5: fix aging counter deallocation
> 
> When a counter is destroyed and used for aging action, the driver should
> remove the counter object from the age-out list if it is there.
> 
> The counter memory of the list entry and of the counter shared
> information is shared because, currently, shared counter cannot be used
> for aging.
> 
> When the support for counter action in action handle API was added, the
> counter shared information was reused and moved to be used also for
> non-shared case. Wrongly, it is used for aging case too.
> 
> Remove the usage of shared information in case of aging.
> 
> Fixes: f3191849f2c2 ("net/mlx5: support flow count action handle")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Matan Azrad <matan@nvidia.com>
> Acked-by: Bing Zhao <bingz@nvidia.com>
> ---

Patch applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh

      reply	other threads:[~2021-06-09 15:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-09 12:32 [dpdk-stable] " Matan Azrad
2021-06-09 15:40 ` 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=DM4PR12MB505441C4532E48E03119FE89CF369@DM4PR12MB5054.namprd12.prod.outlook.com \
    --to=rasland@nvidia.com \
    --cc=bingz@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=stable@dpdk.org \
    --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

patches for DPDK stable branches

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/stable/0 stable/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 stable stable/ https://inbox.dpdk.org/stable \
		stable@dpdk.org
	public-inbox-index stable

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.stable


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git