From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 178] l2fwd application does not work with option '-q'
Date: Fri, 04 Jan 2019 05:43:22 +0000 [thread overview]
Message-ID: <bug-178-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=178
Bug ID: 178
Summary: l2fwd application does not work with option '-q'
Product: DPDK
Version: 18.11
Hardware: All
OS: All
Status: CONFIRMED
Severity: normal
Priority: Normal
Component: examples
Assignee: dev@dpdk.org
Reporter: vipin.varghese@intel.com
Target Milestone: ---
As per
usage description: '-q NQ: number of queue (=ports) per lcore (default is 1)'
documentation description: URL
https://doc.dpdk.org/guides/sample_app_ug/l2_forward_real_virtual.html
To run the application in linuxapp environment with 4 lcores, 16 ports and 8 RX
queues per lcore and MAC address updating enabled, issue the command: $
./build/l2fwd -l 0-3 -n 4 -- -q 8 -p ffff
issue: I am only able to fetch 1 RX queue per port
Checking the code base I find:
1) lcore are mapped to lcores by
/* get the lcore_id for this port */
while (rte_lcore_is_enabled(rx_lcore_id) == 0 ||
lcore_queue_conf[rx_lcore_id].n_rx_port ==
l2fwd_rx_queue_per_lcore) {
rx_lcore_id++;
if (rx_lcore_id >= RTE_MAX_LCORE)
rte_exit(EXIT_FAILURE, "Not enough cores\n");
}
2) but RX queue is setup it is done for 1 rx queue per port
ret = rte_eth_rx_queue_setup(portid, 0, nb_rxd,
rte_eth_dev_socket_id(portid),
&rxq_conf,
l2fwd_pktmbuf_pool);
what is that I am missing to make this work for 1 port with 4 rx queues?
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2019-01-04 5:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 5:43 bugzilla [this message]
2019-05-06 4:33 ` [dpdk-dev] [Bug 178] l2fwd application does not work with option '-q' bugzilla
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=bug-178-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.