DPDK usage discussions
 help / color / mirror / Atom feed
From: Filip Janiszewski <contact@filipjaniszewski.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] Configuring port input set, NIC XL710
Date: Mon, 15 Feb 2021 10:46:27 +0100	[thread overview]
Message-ID: <2a5d34c2-0c04-5e27-c26d-40f49f06b79e@filipjaniszewski.com> (raw)

Hi,

I'm testing an Intel 700-Series (XL710) NIC using testpmd, given the
instructions from here
https://software.intel.com/content/www/us/en/develop/articles/intel-ethernet-controller-700-series-hash-and-flow-director-filters.html
I wanted to modify the inset such that an UDP header checksum would be
taken into account while receiving packets.

To test if it works, I've prepare a bunch of UDP packets all identical
but the checksum - for those packets normal RSS rules fail to split the
traffic across the queues, unless the checksum is taken into account.

I've configured testpmd like this:

./dpdk-testpmd -w 0000:b3:00.0 -- -i --rxq=4 --txq=4 --forward=rxonly

Then:

.
testpmd> port config 0 pctype mapping update 31 31
testpmd> port config 0 pctype 31 hash_inset clear all
testpmd> port config 0 pctype 31 hash_inset set field 32
testpmd> port config all rss 31
.

Where pctype 31 would be "Non-Fragmented IPv4, UDP" and field 32 of the
"field Vector" would be the udp checksum (According to
https://www.intel.com/content/dam/www/public/us/en/documents/datasheets/xl710-10-40-controller-datasheet.pdf
Table 7-12. Default field vector table)

And then started capturing, having set the hash_inset field 32 to
enabled I should be using that particular UDP field (checksum) for hashing.

But, those testpmd commands are not doing much, all the packets end up
all in the same queue even if the checksums are different for all the
packets.

Can anyone help to setup properly testpmd?

Thanks

-- 
BR, Filip
+48 666 369 823

                 reply	other threads:[~2021-02-15  9:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=2a5d34c2-0c04-5e27-c26d-40f49f06b79e@filipjaniszewski.com \
    --to=contact@filipjaniszewski.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).