DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@mellanox.com>
To: Bing Zhao <bingz@mellanox.com>,
	Slava Ovsiienko <viacheslavo@mellanox.com>
Cc: Ori Kam <orika@mellanox.com>, Matan Azrad <matan@mellanox.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] net/mlx5: fix incorrect index when creating flow
Date: Sun, 12 Apr 2020 16:24:04 +0000	[thread overview]
Message-ID: <AM0PR05MB670784A46E8BCB62C9EFEA5DC2DC0@AM0PR05MB6707.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1586443121-281661-1-git-send-email-bingz@mellanox.com>

Hi,
> -----Original Message-----
> From: Bing Zhao <bingz@mellanox.com>
> Sent: Thursday, April 9, 2020 5:39 PM
> To: Slava Ovsiienko <viacheslavo@mellanox.com>; Raslan Darawsheh
> <rasland@mellanox.com>
> Cc: Ori Kam <orika@mellanox.com>; Matan Azrad <matan@mellanox.com>;
> dev@dpdk.org
> Subject: [PATCH v2] net/mlx5: fix incorrect index when creating flow
> 
> When creating a flow, usually the creating routine is called in
> serial. No parallel execution is supported right now. The same
> function will be called only once for a single flow creation.
> But there is a special case that the creating routine will be called
> nested. If the xmeta feature is enabled and there is FLAG / MARK in
> the actions list, some metadata reg copy flow needs to be created
> before the original flow is applied to the hardware.
> In the flow non-cached mode, resources only for flow creation will
> not be saved anymore. The memory space is pre-allocated and reused
> for each flow. A global index for each device is used to indicate
> the memory address of the resources. If the function is called in a
> nested mode, then the index will be reset and make everything get
> corrupted.
> To solve this, a nested index is introduced to save the position for
> the original flow creation. Currently, only one level nested call
> of the flow creating routine is supported.
> 
> Fixes: 9273a26fe267 ("net/mlx5: separate the flow handle resource")
Fixed Fixes ID:  Fixes: da68485be ("net/mlx5: separate the flow handle resource")
> 
> Signed-off-by: Bing Zhao <bingz@mellanox.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
> ---
> v2: fix the typo of email address.
> ---

Patch applied to next-net-mlx,
Kindest regards
Raslan Darawsheh

      reply	other threads:[~2020-04-12 16:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-09 14:31 [dpdk-dev] [PATCH] " Bing Zhao
2020-04-09 14:38 ` [dpdk-dev] [PATCH v2] " Bing Zhao
2020-04-12 16:24   ` 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=AM0PR05MB670784A46E8BCB62C9EFEA5DC2DC0@AM0PR05MB6707.eurprd05.prod.outlook.com \
    --to=rasland@mellanox.com \
    --cc=bingz@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=matan@mellanox.com \
    --cc=orika@mellanox.com \
    --cc=viacheslavo@mellanox.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).