From: wenxu <wenxu@ucloud.cn>
To: Asaf Penso <asafp@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] nvgre inner rss problem in mlx5
Date: Wed, 28 Apr 2021 13:48:19 +0800 (GMT+08:00) [thread overview]
Message-ID: <AG2AnAARFAOPLN2PTXTI54qA.3.1619588899243.Hmail.wenxu@ucloud.cn> (raw)
In-Reply-To: <DM5PR12MB2406BC5C94498D23C09584B8CD409@DM5PR12MB2406.namprd12.prod.outlook.com>
rdma-core version is: rdma-core-52mlnx1-1.52104.x86_64
发件人:Asaf Penso <asafp@nvidia.com>
发送日期:2021-04-28 12:22:32
收件人:"dev@dpdk.org" <dev@dpdk.org>,wenxu <wenxu@ucloud.cn>
主题:Re: [dpdk-dev] nvgre inner rss problem in mlx5
Hello Wenxu,
Thank you for reaching us. I would like to know a few more details before I can provide an assistance.
Can you share the version numbers for:
rdma-core
OFED
OS
Regards,
Asaf Penso
From: dev <dev-bounces@dpdk.org> on behalf of wenxu <wenxu@ucloud.cn>
Sent: Wednesday, April 28, 2021 6:47:45 AM
To: dev@dpdk.org <dev@dpdk.org>
Subject: [dpdk-dev] nvgre inner rss problem in mlx5
Hi mlnx teams,
I test the upstream dpdk with the nvgre inner rss action with dpdk-testpmd
# ./dpdk-testpmd -c 0x1f -n 4 -m 4096 -w "0000:19:00.1" --huge-dir=/mnt/ovsdpdk -- --forward-mode=rxonly --rxq=4 --txq=4 --auto-start --nb-cores=4
# testpmd>> flow create 0 ingress pattern eth / ipv4 / nvgre / end actions rss level 2 types ip udp tcp end queues 0 1 2 3 end / end
Add rte flow for nvgre wit action inner(level 2) rss to the queues 0,1,2,3.
And I test this with the same underlay tunnel but differrent inner ip address/udp ports. But Only one queue recieve the packet.
And if I test this with vxlan case. it works as we expect.
testpmd>> flow create 0 ingress pattern eth / ipv4 / udp / vxlan / end actions rss level 2 types ip udp tcp end queues 0 1 2 3 end / end
# lspci | grep Ether
19:00.0 Ethernet controller: Mellanox Technologies MT27800 Family [ConnectX-5]
19:00.1 Ethernet controller: Mellanox Technologies MT27800 Family [ConnectX-5]
Fw version is 16.29.1016
# ethtool -i net3
driver: mlx5_core
version: 5.12.0-rc4+
firmware-version: 16.29.1016 (MT_0000000080)
Are there any problems for my test case.
BR
wenxu
next prev parent reply other threads:[~2021-04-28 5:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 3:47 wenxu
2021-04-28 4:22 ` Asaf Penso
2021-04-28 5:48 ` wenxu [this message]
2021-04-28 9:31 ` Asaf Penso
2021-04-29 8:29 ` wenxu
2021-04-29 9:06 ` Asaf Penso
2021-05-10 4:53 ` [dpdk-dev] : " wenxu
2021-05-10 8:05 ` Asaf Penso
2021-05-11 3:10 ` wenxu
2021-05-12 18:45 ` Asaf Penso
-- strict thread matches above, loose matches on Subject: below --
2021-08-03 8:44 [dpdk-dev] " wenxu
2021-04-28 3:43 wenxu
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=AG2AnAARFAOPLN2PTXTI54qA.3.1619588899243.Hmail.wenxu@ucloud.cn \
--to=wenxu@ucloud.cn \
--cc=asafp@nvidia.com \
--cc=dev@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).