[Bug 1323] NIC RSS Symmetric hash is not working on Marvell OcteonTx2 (otx2) platform when configuring 4 tuple

[bugzilla@dpdk.org]

[-- Attachment #1: Type: text/plain, Size: 1986 bytes --]

https://bugs.dpdk.org/show_bug.cgi?id=1323

            Bug ID: 1323
           Summary: NIC RSS Symmetric hash is not working on Marvell
                    OcteonTx2 (otx2) platform when configuring 4 tuple
           Product: DPDK
           Version: 20.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: pingtosiva@gmail.com
  Target Milestone: ---

The NIC RSS symmetric hash is not working on the otx2 platform i.e., client to
server and server to client traffic are not hashed to the same core. Below is
code snippet how 4 tuple hashing is enabled on NIC RSS.

As read from a different article, I have tried with symmetric hash_key as 0x00,
0x01 instead of 0x6D,0x5A. Even then symmetric hash is not working.

This is critical for my stateful application development. Kindly provide if
there is a way to implement it. Thanks! in advance.

DPDK version used is 20.11.

#define RSS_HASH_KEY_LENGTH 40
static uint8_t symmetric_hash_key[RSS_HASH_KEY_LENGTH] = {  0x6D, 0x5A, 0x6D,
0x5A, 0x6D, 0x5A, 0x6D, 0x5A,  0x6D, 0x5A, 0x6D, 0x5A, 0x6D, 0x5A, 0x6D, 0x5A, 
0x6D, 0x5A, 0x6D, 0x5A, 0x6D, 0x5A, 0x6D, 0x5A,  0x6D, 0x5A, 0x6D, 0x5A, 0x6D,
0x5A, 0x6D, 0x5A,  0x6D, 0x5A, 0x6D, 0x5A, 0x6D, 0x5A, 0x6D, 0x5A,};uint8_t
symmetric_hash_key_be[RSS_HASH_KEY_LENGTH];

struct rte_eth_conf port_cfg;

port_cfg.rx_adv_conf.rss_conf.rss_hf = (ETH_RSS_UDP | ETH_RSS_TCP |
ETH_RSS_SCTP) | (ETH_RSS_IP & ~ETH_RSS_IPV6_EX);

port_cfg.rx_adv_conf.rss_conf.rss_key_len = RSS_HASH_KEY_LENGTH;

port_cfg.rx_adv_conf.rss_conf.rss_key = symmetric_hash_key;

port_cfg.txmode.mq_mode = ETH_MQ_TX_NONE;

// Other port_cfg params are updated.

rte_eth_dev_configure(port_id, nb_rxq, nb_txq, &port_cfg);

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #2: Type: text/html, Size: 3900 bytes --]