From: Thomas Monjalon <thomas@monjalon.net>
To: Xiaoyu Min <jackmin@mellanox.com>
Cc: dev@dpdk.org, orika@mellanox.com, viacheslavo@mellanox.com,
Adrien Mazarguil <adrien.mazarguil@6wind.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Andrew Rybchenko <arybchenko@solarflare.com>,
stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] ethdev: expand RSS flows based on last item spec
Date: Tue, 05 Nov 2019 11:11:00 +0100 [thread overview]
Message-ID: <4507833.CEzoxxxZIU@xps> (raw)
In-Reply-To: <1580ef9551619fbe0a1f85590cebaf4b026f7f0b.1572944613.git.jackmin@mellanox.com>
Hi Jack,
If it is a fix, please change your title.
05/11/2019 10:16, Xiaoyu Min:
> When rte_flow_expand_rss expands rte_flow item list based on the RSS
> types.
There is no verb in this sentence.
> In another word, it will add some rte_flow items if the user
What is "it"?
> specified items are not complete, for example:
>
> ... pattern eth / end actions rss type tcp end ...
Please explain why it is not complete.
>
> above flow will be expaned to:
>
> ... pattern eth / end actions rss types tcp
> ... pattern eth / ipv4 / tcp / end actions rss types tcp ...
> ... pattern eth / ipv6 / tcp / end actsion rss types tcp ...
There are several typos in this text. Please check.
> However the expansion is just simply expanding items without
> checking last items' spec, means the expanded rules could have conflicting
> settings which is not reasonable and leads to some HW error, for
> example:
This wording is really not clear.
Please make short sentences.
> ... pattern eth type is 0x86DD / end actions rss types tcp ...
>
> is expaneded to:
>
> ... pattern eth type is 0x86DD / ipv4 / tcp end ...
>
> which has conflicting values: 0x86DD vs. ipv4 and HW will refuse create
> flow on some NICs.
>
> This patch will fix above by checking the last item's spec and try to
> complete the item list.
>
> Currently only support to complete item list based on L2/L3 layer.
>
> Fixes: 4ed05fcd441b ("ethdev: add flow API to expand RSS flows")
> Cc: stable@dpdk.org
Missing empty line here to separate blocks.
> Signed-off-by: Xiaoyu Min <jackmin@mellanox.com>
> ---
> lib/librte_ethdev/rte_flow.c | 132 +++++++++++++++++++++++++++++++++--
> 1 file changed, 127 insertions(+), 5 deletions(-)
It's a big change. It needs to be carefully reviewed.
next prev parent reply other threads:[~2019-11-05 10:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 9:16 Xiaoyu Min
2019-11-05 10:11 ` Thomas Monjalon [this message]
2019-11-05 12:08 ` Jack Min
2019-11-05 13:42 ` [dpdk-dev] [PATCH v2] ethdev: fix expand RSS flows Xiaoyu Min
2019-11-06 10:12 ` Ori Kam
2019-11-07 17:02 ` Ferruh Yigit
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=4507833.CEzoxxxZIU@xps \
--to=thomas@monjalon.net \
--cc=adrien.mazarguil@6wind.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jackmin@mellanox.com \
--cc=orika@mellanox.com \
--cc=stable@dpdk.org \
--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).