From: oulijun <oulijun@huawei.com>
To: "orika@mellanox.com" <orika@mellanox.com>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-dev] Questions about rte_flow_create APIs
Date: Fri, 3 Jul 2020 06:44:38 +0000 [thread overview]
Message-ID: <13c6e9a563824423a653bdb64d72d54e@huawei.com> (raw)
Hi, Guys
I am analyzing rte_flow_create API and test and is testing server parametric scenario.
When use testpmd and the following flow creat cmd:
testpmd> flow create 0 ingress pattern end actions rss func simple_xor / end
why the contents of rte_flow_action_rss is not same acquisition method after run the flowing codes.
struct rte_flow_action_rss conf;
rss_conf = action->conf;
the Value of unspecified parameter is not same acquisition method.
The rss_conf.type is default;
The rss_conf.key_len is deault;
The rss_conf.queue_num is deault;
However, the rss_conf.key is random and unpredictable
The result is that when the user does not specify the rss key, the driver will fill a random value into the hardware。
The rss key value found by the user is different from the first value, which results in the user not being able to use it correctly.
I think the reasonable behavior is that either the rss rule was not successfully created or the content of the rss key that was queried has not changed
testpmd> show port 0 rss-hash key
RSS functions:
all ipv4-frag ipv4-other ipv6-frag ipv6-other ip
RSS key:
4439796BB54C5023B675EA5B124F9F30B8A2C03DDFDC4D02A08C9B334AF64A4C05C6FA343958D8557D99583AE138C92E81150366
testpmd> flow create 0 ingress pattern eth / ipv4 / udp / end actions rss types ipv4-udp end queues end / end
Flow rule #0 created
testpmd> show port 0 rss-hash key
RSS functions:
all ipv4-udp udp
RSS key:
74657374706D6427732064656661756C74205253532068617368206B65792C206F7665727269646520697420666F722062657474
What do you think?
Thanks
Lijun Ou
next reply other threads:[~2020-07-03 6:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 6:44 oulijun [this message]
2020-07-05 11:58 ` Ori Kam
2020-07-06 10:59 ` [dpdk-dev] 答复: " oulijun
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=13c6e9a563824423a653bdb64d72d54e@huawei.com \
--to=oulijun@huawei.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=orika@mellanox.com \
--cc=users@dpdk.org \
/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).