From: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
To: xuemingl@nvidia.com, "dev@dpdk.org" <dev@dpdk.org>
Cc: asafp@nvidia.com, matan@nvidia.com, stable@dpdk.org,
viacheslavo@nvidia.com,
"\"dev@dpdk.org; Asaf Penso\" <asafp@nvidia.com>;
Xueming(Steven) Li" <xuemingl@nvidia.com>
Subject: [dpdk-stable] [dpdk-dev] [PATCH] net/mlx5: disable flow dump for Verbs flow
Date: Tue, 6 Oct 2020 08:46:03 +0000 [thread overview]
Message-ID: <1601973963-2540-1-git-send-email-viacheslavo@nvidia.com> (raw)
In-Reply-To: <1599711897-21330-1-git-send-email-xuemingl@nvidia.com>
From: Slava Ovsiienko <viacheslavo@nvidia.com>
-----Original Message-----
From: Slava Ovsiienko
Sent: Sunday, October 4, 2020 19:56
To: Xueming Li <xuemingl@nvidia.com>; Matan Azrad <matan@nvidia.com>
Cc: dev@dpdk.org; Asaf Penso <asafp@nvidia.com>; Xueming(Steven) Li <xuemingl@nvidia.com>; stable@dpdk.org
Subject: RE: [PATCH] net/mlx5: disable flow dump for Verbs flow
> -----Original Message-----
> From: Xueming Li <xuemingl@nvidia.com>
> Sent: Thursday, September 10, 2020 7:26
> To: Matan Azrad <matan@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>
> Cc: dev@dpdk.org; Asaf Penso <asafp@nvidia.com>; Xueming(Steven) Li
> <xuemingl@nvidia.com>; stable@dpdk.org
> Subject: [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>
Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
next prev parent reply other threads:[~2020-10-06 8:46 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 ` Viacheslav Ovsiienko [this message]
2020-10-06 15:24 ` [dpdk-stable] [dpdk-dev] " Raslan Darawsheh
2020-10-07 9:56 ` Ferruh Yigit
2020-10-08 12:09 ` Raslan Darawsheh
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=1601973963-2540-1-git-send-email-viacheslavo@nvidia.com \
--to=viacheslavo@nvidia.com \
--cc=asafp@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=stable@dpdk.org \
--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).