patches for DPDK stable branches
 help / color / Atom feed
From: Raslan Darawsheh <>
To: Suanming Mou <>,
	Slava Ovsiienko <>,
	Matan Azrad <>, "" <>
Cc: "" <>
Subject: Re: [dpdk-stable] [PATCH v2] net/mlx5: fix secondary process resources release
Date: Sun, 31 May 2020 14:03:59 +0000
Message-ID: <> (raw)
In-Reply-To: <>


> -----Original Message-----
> From: Suanming Mou <>
> Sent: Thursday, May 28, 2020 10:00 AM
> To: Slava Ovsiienko <>; Matan Azrad
> <>;
> Cc: Raslan Darawsheh <>;
> Subject: [PATCH v2] net/mlx5: fix secondary process resources release
> When secondary process starts, it will allocate its own process private
> data, and also does remap to UAR register of the Tx queue. Once the
> secondary process exits, these resources should be released accordingly.
> And the shared resources owned by primary should not be touched.
> Currently, once one port in the secondary process spawn failed, all the
> other spawned ports will also be released during process exits. However,
> the mlx5_dev_close() function does not add the cases for secondary
> process, it means call the mlx5_dev_close() function directly in
> secondary process releases the resources it should not touch.
> Add the case for secondary process release to its own resources in
> mlx5_dev_close() function to help it quits gracefully.
> Fixes: 942d13e6e7d1 ("net/mlx5: fix sharing context destroy order")
> Fixes: 3a8207423a0f ("net/mlx5: close all ports on remove")
> Cc:
> Signed-off-by: Suanming Mou <>
> Acked-by: Matan Azrad <>
> ---
> v2: fix more issues in secondary process.
> ---
>  drivers/net/mlx5/mlx5.c      | 47 +++++++++++++++++++++++++++++++-----
> --------

Patch applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh

      reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15  8:42 [dpdk-stable] [PATCH] net/mlx5: fix potential null dereference in port close Suanming Mou
2020-05-28  6:59 ` [dpdk-stable] [PATCH v2] net/mlx5: fix secondary process resources release Suanming Mou
2020-05-31 14:03   ` Raslan Darawsheh [this message]

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

patches for DPDK stable branches

Archives are clonable:
	git clone --mirror 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/ \
	public-inbox-index stable

Newsgroup available over NNTP:

AGPL code for this site: git clone public-inbox