From: Tom Barbette <barbette@kth.se>
To: Bao-Long Tran <tranbaolong@niometrics.com>,
matan@mellanox.com, shahafs@mellanox.com,
viacheslavo@mellanox.com
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Mellanox MLX5 Symmetric RSS
Date: Tue, 28 Apr 2020 13:57:59 +0200 [thread overview]
Message-ID: <2763bd7c-5c08-7c22-4d9f-092597a4e859@kth.se> (raw)
In-Reply-To: <5298AF9A-F06F-4258-AD0C-D481B301D84F@niometrics.com>
Hi,
The trick with symmetric RSS is simply to have a 2-bytes repeating key.
Eg 6D5A repeated 20 times.
Tom
Le 28/04/2020 à 05:14, Bao-Long Tran a écrit :
> Hi,
>
> We're testing the Mellanox NIC MT27800 Family [ConnectX-5] 1017. I wonder if the NIC support symmetric RSS and if yes how to configure it. The input traffic would be a pcap of one single eth/http/tcp flow with both directions., i.e,
> (A) 1.2.3.4:40 -> 5.6.7.8:80
> (B) 5.6.7.8:80 -> 1.2.3.4:40
>
> The desired effect would be to have (A) and (B) hitting the same RX queue.
>
> Below is what I have tried so far with testpmd. So (A) and (B) always hit different RX queues.
>
> testpmd <EAL-options> -- -i -a --nb-cores=16 --forward-mode=rxonly --rxq=8 --txq=8
>
> 1. flow create 0 ingress pattern eth type is 0x0800 / end actions rss / end
>
> 2. low create 0 ingress pattern eth type is 0x0800 / end actions rss queues 0 1 2 3 4 5 6 7 end / end
>
> 3. flow create 0 ingress pattern eth type is 0x0800 / end actions rss func toeplitz level 1 types ipv4 end queues 0 1 2 3 4 5 6 7 end / end
>
> 4. flow create 0 ingress pattern eth type is 0x0800 / end actions rss func toeplitz level 1 types ipv4 end queues 0 1 2 3 4 5 6 7 end key 2CC681D15BDBF4F7FCA28319DB1A3E946B9E38D92C9C03D1AD9944A7D9563D59063C25F3FC1FDC2A key_len 40 / end
>
> Thanks,
> BL
>
prev parent reply other threads:[~2020-04-28 11:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 3:14 Bao-Long Tran
2020-04-28 11:57 ` Tom Barbette [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=2763bd7c-5c08-7c22-4d9f-092597a4e859@kth.se \
--to=barbette@kth.se \
--cc=matan@mellanox.com \
--cc=shahafs@mellanox.com \
--cc=tranbaolong@niometrics.com \
--cc=users@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).