From: <hfli@netitest.com>
To: <declan.doherty@intel.com>, <chas3@att.com>, <dev@dpdk.org>
Subject: [dpdk-dev] 8023ad bond tx crashed if one port has 2 more tx queues
Date: Tue, 19 Mar 2019 17:41:25 +0800 [thread overview]
Message-ID: <001a01d4de37$ec097f80$c41c7e80$@netitest.com> (raw)
Message-ID: <20190319094125._Yzzn3tyAsibmRY7GOPigzlw3HFfJXrmkZJAPPyprdQ@z> (raw)
Hi Guys,
I found a bug in dpdk bond code, while one port has 2 more tx queues, 8023ad
bond port will be crashed in tx burst.
Just analyzed the code below, if 2 more CPU cores send packets on a port by
different tx queue, the arrays like
slave_port_ids/ dist_slave_port_ids/ slave_tx_fail_coun/ slave_bufs will be
shared by all of cores, it will be crashed in this function.
Is there any better solution for this? For now, I just add lock for
rte_eth_tx_burst.
static uint16_t
bond_ethdev_tx_burst_8023ad(void *queue, struct rte_mbuf **bufs,
uint16_t nb_bufs)
{
struct bond_tx_queue *bd_tx_q = (struct bond_tx_queue *)queue;
struct bond_dev_private *internals = bd_tx_q->dev_private;
uint16_t [RTE_MAX_ETHPORTS];
uint16_t slave_count;
uint16_t dist_slave_port_ids[RTE_MAX_ETHPORTS];
uint16_t dist_slave_count;
/* 2-D array to sort mbufs for transmission on each slave into */
struct rte_mbuf *slave_bufs[RTE_MAX_ETHPORTS][nb_bufs];
/* Number of mbufs for transmission on each slave */
uint16_t slave_nb_bufs[RTE_MAX_ETHPORTS] = { 0 };
/* Mapping array generated by hash function to map mbufs to slaves
*/
uint16_t bufs_slave_port_idxs[RTE_MAX_ETHPORTS] = { 0 };
uint16_t slave_tx_count, slave_tx_fail_count[RTE_MAX_ETHPORTS] = {
0 };
uint16_t total_tx_count = 0, total_tx_fail_count = 0;
Thanks and Regards,
Haifeng
next reply other threads:[~2019-03-19 9:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 9:41 hfli [this message]
2019-03-19 9:41 ` hfli
2019-03-19 15:05 ` Chas Williams
2019-03-19 15:05 ` Chas Williams
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='001a01d4de37$ec097f80$c41c7e80$@netitest.com' \
--to=hfli@netitest.com \
--cc=chas3@att.com \
--cc=declan.doherty@intel.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).