DPDK usage discussions
 help / color / mirror / Atom feed
From: shengxiao qian <tedsxqian@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] wrong core receive the package
Date: Thu, 22 Mar 2018 14:40:47 +0800	[thread overview]
Message-ID: <CAPd3biBGCNUSgUj_wjmRsM2MF4JOSC705Z7fdz1TGryhaejWEQ@mail.gmail.com> (raw)
In-Reply-To: <20180321074833.6a3d2656@xeon-e3>

I add some logs,it shows that the packet's hash value is 3104575691
<(310)%20457-5691> and it was received by core 3.
if the function rte_eth_dev_rss_reta_update works well.the  hash
indirection table maybe like this:
    0:       0     1     2     3      4      5      6      7
    8:       8     9    10    11    12    13    14    15
   16:      16  17 18     19    20   21     22     23
   24:      24   25  26   27    28   29     30      31
   32:      32   33  34    35    36    37     38    39
   40:      0     1     2     3      4      5      6      7
   48:      8     9    10    11    12    13    14    15
   56:      16  17 18     19    20   21     22     23
   64:      24   25  26   27    28   29     30      31
   72:      32   33  34    35    36    37     38    39
   80:       0     1     2     3      4      5      6      7
   88:      8     9    10    11    12    13    14    15
   96:     8     9    10    11    12    13    14    15
  104:       24   25  26   27    28   29     30      31
  112:      32   33  34    35    36    37     38    39
  120:       0     1     2     3      4      5      6      7

The hash value 3104575691 <(310)%20457-5691> & 127 = 75,according to the hash
indirection table, the core num 35 is right.But actually it was core3
received.

So i guess may be the hash indirection table is wrong? How can i check this?


2018-03-21 22:48 GMT+08:00 Stephen Hemminger <stephen@networkplumber.org>:

> On Wed, 21 Mar 2018 11:13:19 +0800
> shengxiao qian <tedsxqian@gmail.com> wrote:
>
> > 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?
> >
>
> RSS hash is not symmetrical. The SYN and SYN-ACK packets have swapped
> address and port (src/dest); therefore the hash will be different.
>
> There are some weaker RSS hash keys that are symmetrical.
>

      reply	other threads:[~2018-03-22  6:40 UTC|newest]

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

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=CAPd3biBGCNUSgUj_wjmRsM2MF4JOSC705Z7fdz1TGryhaejWEQ@mail.gmail.com \
    --to=tedsxqian@gmail.com \
    --cc=stephen@networkplumber.org \
    --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).