From: Thomas Monjalon <thomas@monjalon.net>
To: David Liu <dliu@iol.unh.edu>
Cc: dpdk-dev <dev@dpdk.org>,
dts@dpdk.org, Lincoln Lavoie <lylavoie@iol.unh.edu>,
David Marchand <david.marchand@redhat.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Andrew Rybchenko <arybchenko@solarflare.com>,
Ori Kam <orika@mellanox.com>, Ciara Power <ciara.power@intel.com>,
Ivan Ilchenko <ivan.ilchenko@oktetlabs.ru>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Stephen Hemminger <stephen@networkplumber.org>,
Raslan Darawsheh <rasland@mellanox.com>
Subject: Re: [dts] RSS Key Update Feature
Date: Tue, 30 Jun 2020 01:48:14 +0200 [thread overview]
Message-ID: <2250034.MpDbe8kn2E@thomas> (raw)
In-Reply-To: <CAAuqQpREy5uuL_SKKvGGgR73A-0RTN+RD7xjg5YEy-yniuwMTg@mail.gmail.com>
29/06/2020 23:07, David Liu:
> Hello all,
>
> I will be implementing a test in DTS for RSS Key Update.
> http://doc.dpdk.org/guides/nics/features.html#rss-key-update
>
> To my understanding, this feature will test the ability to configure the
> hash key of the ports. If that is incorrect, please let me know.
>
> Configure the port RSS hash key in testpmd and check if the new key will be
> kept. Test configure the hash key that is longer than the max length and
> shorter than the max length.
>
> Then start sending in packets with different source and destination IP
> addresses. Ensure the ports are still able to calculate the hash value from
> the incoming packets.
Updating the key should change the destination queue of the packets.
By setting up multi-queue Rx and choosing IP addresses accordingly,
you can see packets arriving on the expected queue.
> Please let me know if there is anything else need to be tested,
A related test could be to read the computed hash in the mbuf metadata.
next prev parent reply other threads:[~2020-06-29 23:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 21:07 David Liu
2020-06-29 23:48 ` Thomas Monjalon [this message]
2020-06-30 13:01 ` David Liu
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=2250034.MpDbe8kn2E@thomas \
--to=thomas@monjalon.net \
--cc=arybchenko@solarflare.com \
--cc=ciara.power@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dliu@iol.unh.edu \
--cc=dts@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=ivan.ilchenko@oktetlabs.ru \
--cc=lylavoie@iol.unh.edu \
--cc=orika@mellanox.com \
--cc=rasland@mellanox.com \
--cc=stephen@networkplumber.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).