From: Thomas Monjalon <thomas@monjalon.net>
To: "Xueming(Steven) Li" <xuemingl@nvidia.com>
Cc: Slava Ovsiienko <viacheslavo@nvidia.com>,
dev@dpdk.org, Asaf Penso <asafp@nvidia.com>,
"bingz@mellanox.com" <bingz@mellanox.com>,
"stable@dpdk.org" <stable@dpdk.org>,
Matan Azrad <matan@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix nested flow creation error
Date: Fri, 13 Nov 2020 20:22:01 +0100 [thread overview]
Message-ID: <2780604.77yy3yqIK2@thomas> (raw)
In-Reply-To: <MW2PR12MB2492AB26C55D77CBBAE1C036DFE80@MW2PR12MB2492.namprd12.prod.outlook.com>
> > 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>
Applied in next-net-mlx, thanks.
prev parent reply other threads:[~2020-11-13 19:22 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
2020-11-13 19:22 ` Thomas Monjalon [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=2780604.77yy3yqIK2@thomas \
--to=thomas@monjalon.net \
--cc=asafp@nvidia.com \
--cc=bingz@mellanox.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--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
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).