DPDK usage discussions
 help / color / mirror / Atom feed
From: Jun Gan <geminijun@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Asaf Penso <asafp@mellanox.com>,
	"users@dpdk.org" <users@dpdk.org>,
	 Technical Support <support@mellanox.com>
Subject: Re: [dpdk-users] Same 5 tuple UDP packets have been delivered to different queues.
Date: Wed, 9 Oct 2019 21:04:57 -0700	[thread overview]
Message-ID: <CABzhwkNo0ZYe0+LqmTLQCu__UCs8C5Qtg9oh5pYzQj5Pbe+wog@mail.gmail.com> (raw)
In-Reply-To: <20191009180856.41575900@hermes.lan>

Hi Stephen,

Thanks for the help, it turns out that it's because of a coding error.

I have fixed that and it's working well now.


On Wed, Oct 9, 2019 at 6:09 PM Stephen Hemminger <stephen@networkplumber.org>
wrote:

> On Tue, 8 Oct 2019 21:29:46 -0700
> Jun Gan <geminijun@gmail.com> wrote:
>
> > Hi Stephen,
> >
> > Thanks for the suggestion, I actually tried both, but no difference, the
> > problem for me is that same src&dsp ip&port udp packets, will be
> delivered
> > to different queues.
> >
> > That breaks my assumption that the packet from some session will be
> > processed by the same thread on the server.
> >
> > so besides rx_adv_conf, is there any other things I have to configure?
>
> What is value of rss_hash in the received packet, is it the same?
> Also what environment HW, NIC, etc?
>


-- 
Jun Gan

      reply	other threads:[~2019-10-10  4:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-07  3:12 Jun Gan
2019-10-08 11:52 ` Asaf Penso
2019-10-09  1:56   ` Jun Gan
2019-10-09  3:12     ` Stephen Hemminger
2019-10-09  4:29       ` Jun Gan
2019-10-10  1:08         ` Stephen Hemminger
2019-10-10  4:04           ` Jun Gan [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=CABzhwkNo0ZYe0+LqmTLQCu__UCs8C5Qtg9oh5pYzQj5Pbe+wog@mail.gmail.com \
    --to=geminijun@gmail.com \
    --cc=asafp@mellanox.com \
    --cc=stephen@networkplumber.org \
    --cc=support@mellanox.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).