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 v2] net/mlx5: fix sample and mirror use incorrect devices
Date: Thu, 19 Nov 2020 08:24:44 +0000	[thread overview]
Message-ID: <DM6PR12MB2748563E059471C149DC51FBCFE00@DM6PR12MB2748.namprd12.prod.outlook.com> (raw)
In-Reply-To: <1605748787-65361-1-git-send-email-suanmingm@nvidia.com>

Hi,

> -----Original Message-----
> From: Suanming Mou <suanmingm@nvidia.com>
> Sent: Thursday, November 19, 2020 3:20 AM
> To: Slava Ovsiienko <viacheslavo@nvidia.com>; Matan Azrad
> <matan@nvidia.com>
> Cc: dev@dpdk.org; Raslan Darawsheh <rasland@nvidia.com>
> Subject: [PATCH v2] net/mlx5: fix sample and mirror use incorrect devices
> 
> The sample and mirror action objects are maintained on the list
> shared between the ports belonging to the same multiport Infiniband
> device(between representors).
> 
> The actions in the NIC steering domains might contain the references
> to the sub-flow action objects created over the given port. The action
> deletion might happen in the context of the different port and on the
> deletion of referenced objects the incorrect port might be specified.
> To avoid this we should save the port on what the sub-flow actions
> were created and then use this saved port for sub-flow action release.
> 
> This commit saves the create device in the sample and mirror actions
> struct to avoid using the incorrect port device in releasing.
> 
> Fixes: 19784141692e ("net/mlx5: make sample and mirror action thread
> safe")
> 
> Signed-off-by: Suanming Mou <suanmingm@nvidia.com>
> Reviewed-by: Jiawei Wang <jiaweiw@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> ---
> 
> v2:
>  - Commit message updated.
> 
> ---

Patch applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-16  2:31 [dpdk-dev] [PATCH] " Suanming Mou
2020-11-19  1:19 ` [dpdk-dev] [PATCH v2] " Suanming Mou
2020-11-19  8: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=DM6PR12MB2748563E059471C149DC51FBCFE00@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 \
    /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).