DPDK usage discussions
 help / color / mirror / Atom feed
From: Pavel Vazharov <freakpv@gmail.com>
To: users <users@dpdk.org>
Subject: [dpdk-users] Question about RSS hash function
Date: Tue, 10 Nov 2020 11:05:40 +0200	[thread overview]
Message-ID: <CAK9EM1_hEk_Wy5wv-F8dDQ+Zj1RQF7ZO1AM+gtLDsrueTbyJ+w@mail.gmail.com> (raw)

Hi there,

We are testing doing some tests with DPDK 19.11.5 and Intel 82599ES
10-Gigabit SFI/SFP+ NIC.
In our scenario we need to make sure that all packets with given
source/destination IPs go on the same queue no matter if they are
fragmented or not.
So, per my understanding, we need the device to support ETH_RSS_IP or at
least (ETH_RSS_IPV4|ETH_RSS_FRAG_IPV4|ETH_RSS_IPV6|ETH_RSS_FRAG_IPV6).
However, the field rte_eth_dev_info.flow_type_rss_offloads reports that
this device supports only (ETH_RSS_IPV4|ETH_RSS_IPV6|ETH_RSS_IPV6_EX).
Here are my questions:
1. It seems to me that the device doesn't support RSS for IPv4/IPv6
fragments?
2. What can be done to achieve the wanted packet distribution if we can't
use the RSS? Do we need to use the rte_flow_* functions?

Thanks,
Pavel.

                 reply	other threads:[~2020-11-10  9:05 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=CAK9EM1_hEk_Wy5wv-F8dDQ+Zj1RQF7ZO1AM+gtLDsrueTbyJ+w@mail.gmail.com \
    --to=freakpv@gmail.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).