DPDK patches and discussions
 help / color / mirror / Atom feed
From: Sergey Balabanov <balabanovsv@ecotelecom.ru>
To: dev <dev@dpdk.org>
Subject: [dpdk-dev] Bond port with multiple queues
Date: Wed, 02 Dec 2015 16:11:01 +0300	[thread overview]
Message-ID: <1798136.BiEt3LMkbp@stand> (raw)

Hello,

I configured a bond port with 2 rx queues on it and added 2 slaves into the 
bond port. When I run traffic I get all packets on queue #0. This is quite 
expected when RSS turned off. When I turn on RSS all packets are distributed 
between two rx queues. There is no guarantee that I will get all packets from 
the slave port #0 on some queue and all packets from the slave port #1 on 
another queue.
Does anybody know is there a way to configure bond port in a way when all traffic 
on port #0 goes to queue #0 and traffic on port #1 goes to queue #1?

Thanks,
Sergey Balabanov

             reply	other threads:[~2015-12-02 13:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-02 13:11 Sergey Balabanov [this message]
2015-12-02 15:49 ` Declan Doherty

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=1798136.BiEt3LMkbp@stand \
    --to=balabanovsv@ecotelecom.ru \
    --cc=dev@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).