patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Matan Azrad <matan@nvidia.com>
To: "Xueming(Steven) Li" <xuemingl@nvidia.com>,
	Slava Ovsiienko <viacheslavo@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Xueming(Steven) Li" <xuemingl@nvidia.com>,
	 Asaf Penso <asafp@nvidia.com>,
	"bingz@mellanox.com" <bingz@mellanox.com>,
	 "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] net/mlx5: fix nested flow creation error
Date: Wed, 11 Nov 2020 08:53:26 +0000
Message-ID: <MW2PR12MB2492AB26C55D77CBBAE1C036DFE80@MW2PR12MB2492.namprd12.prod.outlook.com> (raw)
In-Reply-To: <1604962679-20351-1-git-send-email-xuemingl@nvidia.com>



 From: Xueming Li 
> If xmedata mode 1 enabled and create a flow with RSS and mark action, there
> was an error that rdma-core failed to create RQT due to wrong queue
> definition. This was due to mixed flow creation in thread specific flow
> workspace.
> 
> This patch introduces nested flow workspace(context data), each flow uses
> dedicate flow workspace, pop and restore workspace when nested flow
> creation done, the original flow with continue with original flow workspace.
> The total number of thread specific flow workspace should be
> 2 due to only one nested flow creation scenario so far.
> 
> Fixes: 8bb81f2649b1 ("net/mlx5: use thread specific flow workspace")
> Fixes: 3ac3d8234b82 ("net/mlx5: fix index when creating flow")
> Cc: bingz@mellanox.com
> Cc: stable@dpdk.org
> 
> Signed-off-by: Xueming Li <xuemingl@nvidia.com>
Acked-by: Matan Azrad <matan@nvidia.com>

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-09 22:57 Xueming Li
2020-11-11  8:53 ` Matan Azrad [this message]
2020-11-13 19:22   ` [dpdk-stable] [dpdk-dev] " Thomas Monjalon

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=MW2PR12MB2492AB26C55D77CBBAE1C036DFE80@MW2PR12MB2492.namprd12.prod.outlook.com \
    --to=matan@nvidia.com \
    --cc=asafp@nvidia.com \
    --cc=bingz@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    --cc=viacheslavo@nvidia.com \
    --cc=xuemingl@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