DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Montorsi, Francesco" <fmontorsi@empirix.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] how to use multiple RX queues on the same port
Date: Mon, 26 Oct 2015 17:22:45 +0000	[thread overview]
Message-ID: <13d836797e6944cca262c12cfb26a743@bilemail1.empirix.com> (raw)

Hi all,
To avoid rx_nombuf packet drops, I'm trying to configure a DPDK port to use more than 1 RX queue... so I'm trying (on a 10Gbps card) to use 4 RX queues.
The call to rte_eth_dev_configure() and the 4 calls to rte_eth_rx_queue_setup() succeed but then via the rte_eth_rx_queue_count() API I see that only the first RX queue is used. The remaining 3 seems unused... am I missing something?


Thanks!

Francesco Montorsi

             reply	other threads:[~2015-10-26 17:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-26 17:22 Montorsi, Francesco [this message]
2015-10-26 19:36 ` De Lara Guarch, Pablo
2015-10-27 10:12   ` Montorsi, Francesco

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=13d836797e6944cca262c12cfb26a743@bilemail1.empirix.com \
    --to=fmontorsi@empirix.com \
    --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).