From: Raslan Darawsheh <rasland@mellanox.com>
To: Matan Azrad <matan@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Slava Ovsiienko <viacheslavo@mellanox.com>,
Bing Zhao <bingz@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/mlx5: fix flow table hash list conversion
Date: Sun, 17 Nov 2019 14:13:24 +0000 [thread overview]
Message-ID: <DB3PR0502MB39645AF4ABFBD4F484DE67C6C2720@DB3PR0502MB3964.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1573992894-5949-1-git-send-email-matan@mellanox.com>
Hi,
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Matan Azrad
> Sent: Sunday, November 17, 2019 2:15 PM
> To: dev@dpdk.org
> Cc: Slava Ovsiienko <viacheslavo@mellanox.com>; Bing Zhao
> <bingz@mellanox.com>
> Subject: [dpdk-dev] [PATCH v2] net/mlx5: fix flow table hash list conversion
>
> For the case when DR is not supported and DV is supported:
> multi-tables feature is off.
> In this case, only table 0 is supported.
> Table 0 structure wrongly was not created what prevented any
> matcher object to be created and even caused crashes.
>
> Create the table hash list in DV case too.
> Create table zero empty structure for each domain when DR is not
> supported.
> Allow NULL DR internal table object to be used.
>
> Fixes: 860897d2895a ("net/mlx5: reorganize flow tables with hash list")
> Cc: bingz@mellanox.com
>
> Signed-off-by: Matan Azrad <matan@mellanox.com>
> ---
>
> V2:
> Fix checkpatch warnings.
>
Fixed issue with check patch (removed extra empty line)
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2019-11-17 14:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 16:22 [dpdk-dev] [PATCH] " Matan Azrad
2019-11-17 12:14 ` [dpdk-dev] [PATCH v2] " Matan Azrad
2019-11-17 14:13 ` 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=DB3PR0502MB39645AF4ABFBD4F484DE67C6C2720@DB3PR0502MB3964.eurprd05.prod.outlook.com \
--to=rasland@mellanox.com \
--cc=bingz@mellanox.com \
--cc=dev@dpdk.org \
--cc=matan@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).