DPDK patches and discussions
 help / color / mirror / Atom feed
From: Deepak Gowda <deepak.dt06@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] RSS hash computation on Intel X550 NIC with ixgbe driver
Date: Tue, 6 Apr 2021 00:00:55 +0530	[thread overview]
Message-ID: <CAM84qfqUfE8TZ4eVFVNH2=P89X1rkHzv09c=GYbZ37WyqPruFw@mail.gmail.com> (raw)

Hello,

I have been doing some experiments on rss hash computation, i'm using
DPDK's testpmd application. Even though I apply rss conf on the
available DPDK port, i don't see any value populated in the rss hash, it's
always zero.

Setup details --
*Debian 10 VM with a (Intel X550) VF attached to it.*
*DPDK version* *-* dpdk-18.11.2
*NIC - *
root@debian:~# lspci | grep -i ether
00:03.0 Ethernet controller: Red Hat, Inc Virtio network device

*00:09.0 Ethernet controller: Intel Corporation X550 Virtual Function**DPDK
dev_bind o/p -*
root@debian:~/dpdk-stable-18.11.2/usertools# ./dpdk-devbind.py --status
Network devices using DPDK-compatible driver
============================================
0000:00:09.0 'X550 Virtual Function 1565' drv=igb_uio unused=ixgbevf

Network devices using kernel driver
===================================
0000:00:03.0 'Virtio network device 1000' if=ens3 drv=virtio-pci
unused=virtio_pci,igb_uio *Active*

No 'Crypto' devices detected
============================

No 'Eventdev' devices detected
==============================

No 'Mempool' devices detected
=============================

No 'Compress' devices detected
==============================
root@debian:~/dpdk-stable-18.11.2/usertools#

*This is how launch test pmd -* ./testpmd -l 0-3 -n 4 -- -i --portmask=0x1
--nb-cores=2
Then, when the testpmd is up, i issue the following commands on the testpmd
cli -- in the same order as below
testpmd> set fwd rxonly
Set rxonly packet forwarding mode
testpmd> start
rxonly packet forwarding - ports=1 - cores=1 - streams=1 - NUMA support
enabled, MP allocation mode: native
Logical Core 1 (socket 0) forwards packets on 1 streams:
  RX P=0/Q=0 (socket 0) -> TX P=0/Q=0 (socket 0) peer=02:00:00:00:00:00

  rxonly packet forwarding packets/burst=32
  nb forwarding cores=2 - nb forwarding ports=1
  port 0: RX queue number: 1 Tx queue number: 1
    Rx offloads=0x0 Tx offloads=0x0
    RX queue: 0
      RX desc=512 - RX free threshold=32
      RX threshold registers: pthresh=8 hthresh=8  wthresh=0
      RX Offloads=0x0
    TX queue: 0
      TX desc=512 - TX free threshold=32
      TX threshold registers: pthresh=32 hthresh=0  wthresh=0
      TX offloads=0x0 - TX RS bit threshold=32
testpmd> port config all rss all
Port 0 modified RSS hash function based on hardware
support,requested:0x3fffc configured:0

After this I send udp packets from another machine and I see 0x0 in the
hash field on all the received packets. Am i missing something here?
Do I need to configure anything on the host machine or the PF?
Any insight is appreciated. Thanks!

-Deepak Gowda

                 reply	other threads:[~2021-04-05 18:31 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='CAM84qfqUfE8TZ4eVFVNH2=P89X1rkHzv09c=GYbZ37WyqPruFw@mail.gmail.com' \
    --to=deepak.dt06@gmail.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).