DPDK patches and discussions
 help / color / mirror / Atom feed
From: Heung Sik Choi <hschoi@os.korea.ac.kr>
To: dev@dpdk.org
Subject: [dpdk-dev] Is it possible to make softrss value be same with NIC RSS value?
Date: Fri, 26 May 2017 12:54:39 +0900	[thread overview]
Message-ID: <CAAZV7DDfh=f=FOv3FnT9OrCF7aG7t0b3CJr2_u1kMbgWrf7MKQ@mail.gmail.com> (raw)

Hi,

I study hash optimization in network, and  I know that rte_softrss()
function in DPDK lib(rte_thash.h) which implements RSS. And then, I guess
that its value is same with NIC RSS(hardware).

I get NIC RSS by call 'le32_to_cpu(rx_desc->wb.lower.hi_dword.rss)';

However, I printed NIC RSS's value and Soft RSS value, and two values is
different. I thought that because of little endian, they are different. So
I change the call with  'be32_to_cpu(rx_desc->wb.lower.hi_dword.rss)'. But,
the result is same

Is my guess wrong?

 Please let me know if you have any insights.

                 reply	other threads:[~2017-05-26  3:54 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='CAAZV7DDfh=f=FOv3FnT9OrCF7aG7t0b3CJr2_u1kMbgWrf7MKQ@mail.gmail.com' \
    --to=hschoi@os.korea.ac.kr \
    --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).