DPDK usage discussions
 help / color / mirror / Atom feed
From: shengxiao qian <tedsxqian@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] wrong core receive the package
Date: Wed, 21 Mar 2018 11:13:19 +0800	[thread overview]
Message-ID: <CAPd3biDbxRohHLENKijwSthiEWCspFoGRV8ypLHkmSyPR+ABaw@mail.gmail.com> (raw)

Hi there;
    Our machine has 2 cpus(Intel(R) Xeon(R) CPU E5-2630 v4 @ 2.20GHz)with
40 cores.
If the core num is less than or equal to 16. the application with dpdk
works fine.But if the core num more than 16.there is something wrong with
it.
    In our test scenario(more then 16 cores), server a is a tcp client and
server b is a tcp server. Server a sends a syn packet to server B with
core1, and server B returns a syn ack message to server a.Although the hash
value of these two packets is the same, syn ack packets are distributed to
server a other core(not the send core),Can anyone give some help?

NIC info:
 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network
Connection(recv 01)

I reconnect the nic to Linux and examine it with ethtool:

RX flow hash indirection table for enp4s0f1 with 40 RX ring(s):
    0:      0     1     2     3     4     5     6     7
    8:      8     9    10    11    12    13    14    15
   16:      0     1     2     3     4     5     6     7
   24:      8     9    10    11    12    13    14    15
   32:      0     1     2     3     4     5     6     7
   40:      8     9    10    11    12    13    14    15
   48:      0     1     2     3     4     5     6     7
   56:      8     9    10    11    12    13    14    15
   64:      0     1     2     3     4     5     6     7
   72:      8     9    10    11    12    13    14    15
   80:      0     1     2     3     4     5     6     7
   88:      8     9    10    11    12    13    14    15
   96:      0     1     2     3     4     5     6     7
  104:      8     9    10    11    12    13    14    15
  112:      0     1     2     3     4     5     6     7
  120:      8     9    10    11    12    13    14    15
RSS hash key:
64:8e:94:4d:41:6e:5b:84:47:49:df:34:e0:f2:6c:4f:cf:1e:c7:ec:f2:ff:e5:dc:a1:10:85:58:4e:af:f4:a7:98:f4:77:94:5b:d3:27:49
RSS hash function:
    toeplitz: on
    xor: off


RSS related configuration and code :

1:rxmode_mq_mode = ETH_MQ_RX_RSS
2:rx_adv_conf.rss_conf.rss_hf = ETH_RSS_PROTO_MASK

           3:

void dpdk_device::set_rss_table()

{

    if (_dev_info.reta_size == 0)

        return;


    int reta_conf_size =std::max(1, _dev_info.reta_size /
RTE_RETA_GROUP_SIZE);

    rte_eth_rss_reta_entry64 reta_conf[reta_conf_size];//reta_conf_size=2


    // Configure the HW indirection table

    unsigned i = 0;

    for (auto& x : reta_conf) {

        x.mask = ~0ULL;

        for (auto& r: x.reta) {

            r = i++ % _num_queues;//_num_queues = 40

        }

    }


    if (rte_eth_dev_rss_reta_update(_port_idx, reta_conf,
_dev_info.reta_size)) {

        rte_exit(EXIT_FAILURE, "Port %d: Failed to update an RSS
indirection table", _port_idx);

    }


  }



is there anything wrong with the congigure?

             reply	other threads:[~2018-03-21  3:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-21  3:13 shengxiao qian [this message]
2018-03-21 14:48 ` Stephen Hemminger
2018-03-22  6:40   ` shengxiao qian

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=CAPd3biDbxRohHLENKijwSthiEWCspFoGRV8ypLHkmSyPR+ABaw@mail.gmail.com \
    --to=tedsxqian@gmail.com \
    --cc=users@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).