DPDK patches and discussions
 help / color / mirror / Atom feed
From: Rahul Ramachandran <rahulnitk2004@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] IPV6 RSS not working in i40e
Date: Tue, 16 Feb 2016 17:14:44 +0530	[thread overview]
Message-ID: <CAOwLgip7yTCyD1uH3qRNVy5Qy55Oeu6uzHpRzu0rFRC2B+VBew@mail.gmail.com> (raw)

Hi,

    I am using dpdk 2.1. I see the hash flags are unified compared to my
previous version 1.8.
    But with DPDK 2.1 in Fortville NIC's, I see ipv6 RSS is not working,
all the frames are queued to
    first queue even though I have 16 queues (RETA table looks correct).

    For IPV4 RSS works as expected in Fortville. Also in 10G, both ipv4 and
ipv6 RSS works.

    My RSS configuration is : rss_hf = ETH_RSS_IP | ETH_*RSS*
_NONFRAG_IPV4_TCP | ETH_*RSS*_NONFRAG_IPV4_UDP

    I see ETH_RSS_IP contains Layer3 hash flags for ipv6.

    #define ETH_*RSS*_IP ( \
              ETH_*RSS*_IPV4 | \
              ETH_*RSS*_FRAG_IPV4 | \
              ETH_*RSS*_NONFRAG_IPV4_OTHER | \
              ETH_*RSS*_*IPV6* | \
              ETH_*RSS*_FRAG_*IPV6* | \
              ETH_*RSS*_NONFRAG_*IPV6*_OTHER | \
              ETH_*RSS*_*IPV6*_EX)

    But when I query the hash flags, I get the value of 8888. I understand
while configuring RSS
    HF in the 40G NIC, we mask the configured RSS HF with NIC specific mask
flags before writing to NIC. But I am not
    sure after masking it is taking the flags for IPV6.

    The mask or I40E:            I40E_*RSS*_OFFLOAD_ALL    . I see this
conatins the flags ETH_*RSS*_FRAG_*IPV6 & *ETH_*RSS*_NONFRAG_*IPV6*_OTHER.

    Are you aware of any such problems?

    Please let me know if you need more information.

Thanks

             reply	other threads:[~2016-02-16 11:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-16 11:44 Rahul Ramachandran [this message]
2016-02-16 13:50 ` Rahul Ramachandran

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=CAOwLgip7yTCyD1uH3qRNVy5Qy55Oeu6uzHpRzu0rFRC2B+VBew@mail.gmail.com \
    --to=rahulnitk2004@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).