patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
	"Xueming(Steven) Li" <xuemingl@nvidia.com>,
	Matan Azrad <matan@nvidia.com>,
	Slava Ovsiienko <viacheslavo@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Asaf Penso <asafp@nvidia.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] net/mlx5: disable flow dump for Verbs flow
Date: Thu, 8 Oct 2020 12:09:21 +0000	[thread overview]
Message-ID: <DM6PR12MB2748B5871D9489F00CA059F7CF0B0@DM6PR12MB2748.namprd12.prod.outlook.com> (raw)
In-Reply-To: <8210b384-e788-3aa3-aeaf-7a52687a1b72@intel.com>

Hi,
> -----Original Message-----
> From: Ferruh Yigit <ferruh.yigit@intel.com>
> Sent: Wednesday, October 7, 2020 12:56 PM
> To: Raslan Darawsheh <rasland@nvidia.com>; Xueming(Steven) Li
> <xuemingl@nvidia.com>; Matan Azrad <matan@nvidia.com>; Slava
> Ovsiienko <viacheslavo@nvidia.com>
> Cc: dev@dpdk.org; Asaf Penso <asafp@nvidia.com>; stable@dpdk.org
> Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] net/mlx5: disable flow dump
> for Verbs flow
> 
> On 10/6/2020 4:24 PM, Raslan Darawsheh wrote:
> > Hi,
> >
> >> -----Original Message-----
> >> From: dev <dev-bounces@dpdk.org> On Behalf Of Xueming Li
> >> Sent: Thursday, September 10, 2020 7:25 AM
> >> To: Matan Azrad <matan@nvidia.com>; Slava Ovsiienko
> >> <viacheslavo@nvidia.com>
> >> Cc: dev@dpdk.org; Asaf Penso <asafp@nvidia.com>; stable@dpdk.org
> >> Subject: [dpdk-dev] [PATCH] net/mlx5: disable flow dump for Verbs flow
> >>
> >> There was a segment fault when dump flows with device argument of
> >> dv_flow_en=0. In such case, Verbs flow engine was enabled and fdb
> >> resources were not initialized. It's suggested to use mlx_fs_dump
> >> for Verbs flow dump.
> >>
> >> This patch adds verbs engine check, prints warning message and return
> >> gracefully.
> >>
> >> Cc: stable@dpdk.org
> >> Signed-off-by: Xueming Li <xuemingl@nvidia.com>
> 
> Can you please provide the fixed commit information?
> That is required to figure out which stable tress to backport.
Fixes: f6d7202402c9 ("net/mlx5: support flow dump API")

Just added to next-net-mlx tree and pushed 

Kindest regards
Raslan Darawsheh

      reply	other threads:[~2020-10-08 12:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-10  4:24 [dpdk-stable] " Xueming Li
2020-10-06  8:46 ` [dpdk-stable] [dpdk-dev] " Viacheslav Ovsiienko
2020-10-06 15:24 ` Raslan Darawsheh
2020-10-07  9:56   ` Ferruh Yigit
2020-10-08 12:09     ` 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=DM6PR12MB2748B5871D9489F00CA059F7CF0B0@DM6PR12MB2748.namprd12.prod.outlook.com \
    --to=rasland@nvidia.com \
    --cc=asafp@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --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).