* [dpdk-dev] [Bug 178] l2fwd application does not work with option '-q'
@ 2019-01-04 5:43 bugzilla
2019-05-06 4:33 ` bugzilla
0 siblings, 1 reply; 3+ messages in thread
From: bugzilla @ 2019-01-04 5:43 UTC (permalink / raw)
To: dev
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-05-06 4:33 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-01-04 5:43 [dpdk-dev] [Bug 178] l2fwd application does not work with option '-q' bugzilla
2019-05-06 4:33 ` bugzilla
2019-05-06 4:33 ` bugzilla
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).