DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Hanoch Haim (hhaim)" <hhaim@cisco.com>,
	Bruce Richardson <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] i40e mbuf->rss indication
Date: Thu, 22 Mar 2018 12:18:16 +0000	[thread overview]
Message-ID: <856b65d4-a35f-3b2e-73d4-dbfdf105b9c6@intel.com> (raw)
In-Reply-To: <ec9c18bf00824413af21053d27fb1427@XCH-RTP-017.cisco.com>

On 3/22/2018 11:46 AM, Hanoch Haim (hhaim) wrote:
> Driver: i40e
> 
> DPDK : 17.11
> 
> Configuration : 
> 
> 1)     RSS configuration 
>        rxmode.mq_mode = ETH_MQ_RX_RSS;
>        rss->rss_hf = ETH_RSS_UDP | ETH_RSS_TCP;
>        rss->rss_key = Microsoft key 
>        rss->rss_key_len = 52
> 
>        *configure RETA to some rx-queues
> 
> 2)        Change hash to TOEPLITZ (only for i40e)
> 
>           struct rte_eth_hash_filter_info info = {};
>           info.info_type = RTE_ETH_HASH_FILTER_GLOBAL_CONFIG;
>           info.info.global_conf.hash_func = RTE_ETH_HASH_FUNCTION_TOEPLITZ;
>           rte_eth_dev_filter_ctrl(m_repid, 
>                                   RTE_ETH_FILTER_HASH,
>                                   RTE_ETH_FILTER_SET, &info);
> 
> 3) Configure some flow-director rules 
> 
> 4) TCP/UDP packets are received to the *right* core (based on a SW Toeplitz calculation +reta table) however
>    The reported rss value is *wrong* in the mbuf 
>   (m->hash.rss == *wrong value*)

Are you getting same result with both scalar and vector driver?

>   ((m->ol_flags&PKT_RX_RSS_HASH) == PKT_RX_RSS_HASH
> 
> 5) The above works fine for mlx5 and ixgbe
> 
> 6) I suspect the hash is something else, maybe flow-director id or xor hash ..
> 
> Wanted to know if this is a known issue. I can provide a simple way to reproduce it using TRex 
> 
> Thanks,
> Hanoh
> 
> 
> -----Original Message-----
> From: Bruce Richardson [mailto:bruce.richardson@intel.com] 
> Sent: Thursday, March 22, 2018 1:35 PM
> To: Hanoch Haim (hhaim)
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] i40e mbuf->rss indication
> 
> On Wed, Mar 21, 2018 at 06:47:22PM +0000, Hanoch Haim (hhaim) wrote:
>> Hi All,
>> DPDK:17.11
>> When i40e is configured with RSS enabled and hash.type=toeplitz
>>
>> m->hash.rss = some weird number
>> ((m->ol_flags&PKT_RX_RSS_HASH) == PKT_RX_RSS_HASH
>>
>> The hash value is correct and match the MS Toeplitz standard.
>>
>> Is this expected?
> 
> I'm sorry, but I don't quite follow the question, or the problem. Are you meaning to say that the hash value is incorrect, or that the flag is not being set or something else?
> 
> /Bruce
> 
>>
>> The above works fine with ixgbe/mlx5
>>
>> Thanks,
>> Hanoh
>>

  reply	other threads:[~2018-03-22 12:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-21 18:47 Hanoch Haim (hhaim)
2018-03-22 11:34 ` Bruce Richardson
2018-03-22 11:46   ` Hanoch Haim (hhaim)
2018-03-22 12:18     ` Ferruh Yigit [this message]
2018-03-22 12:52       ` Hanoch Haim (hhaim)
2018-03-22 14:21         ` Bruce Richardson
2018-03-25 18:19           ` Chilikin, Andrey
2018-03-25 21:54             ` Hanoch Haim (hhaim)

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=856b65d4-a35f-3b2e-73d4-dbfdf105b9c6@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=hhaim@cisco.com \
    /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).