From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 116] Single-port, multi-core and multi-queue mode (open RSS), when configuring IP, may cause dpdk coredump
Date: Wed, 05 Dec 2018 03:01:37 +0000 [thread overview]
Message-ID: <bug-116-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=116
Bug ID: 116
Summary: Single-port, multi-core and multi-queue mode (open
RSS), when configuring IP, may cause dpdk coredump
Product: DPDK
Version: unspecified
Hardware: x86
OS: Linux
Status: CONFIRMED
Severity: critical
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: he.qiao17@zte.com.cn
Target Milestone: ---
Coredump stack information：
Thread 153 "lcore-slave-1" received signal SIGSEGV, Segmentation fault.
#0 0x00007ffff37b570d in ixgbe_rxq_rearm (rxq=0x7ffd4e5ed680) at
ixgbe_rxtx_vec_sse.c:98
#1 0x00007ffff37b6740 in _recv_raw_pkts_vec (rxq=0x7ffd4e5ed680,
rx_pkts=0x926db0 <app+597232>, nb_pkts=32, split_packet=0x7fff227f5820 "")at
xgbe_rxtx_vec_sse.c:290
#2 0x00007ffff37b743b in ixgbe_recv_scattered_pkts_vec
(rx_queue=0x7ffd4e5ed680, rx_pkts=0x926db0 <app+597232>, nb_pkts=144) at
ixgbe_rxtx_vec_sse.c:502
#3 0x0000000000515bd1 in rte_eth_rx_burst (port_id=0 '\000', queue_id=0,
rx_pkts=0x926db0 <app+597232>, nb_pkts=144) at rte_ethdev.h:2659
#4 0x000000000051c1b4 in app_lcore_io_rx
My dpdk IO rx/tx queue configuration is as follows:
--rx (0,0,1),(0,1,9),(0,2,17) --tx (0,1)
one core corresponds to one queue, using multiple queues.
When configuring IP, function rte_kni_handle_request() can get the
RTE_KNI_REQ_CFG_NETWORK_IF message from the kernel. At this time,
rte_eth_dev_stop will be called. All the queue information on the current port
will be cleared in this process, but some queues are being used by other cores.
rte_eth_dev_stop() -> ixgbe_dev_stop() -> ixgbe_dev_clear_queues() ->
ixgbe_rx_queue_release_mbufs()
void __attribute__((cold))
ixgbe_dev_clear_queues(struct rte_eth_dev *dev)
{
...
for (i = 0; i < dev->data->nb_rx_queues; i++) {
struct ixgbe_rx_queue *rxq = dev->data->rx_queues[i];
...
}
}
static inline void
_ixgbe_rx_queue_release_mbufs_vec(struct ixgbe_rx_queue *rxq)
{
...
/* set all entries to NULL */
memset(rxq->sw_ring, 0, sizeof(rxq->sw_ring[0]) * rxq->nb_rx_desc);
}
The reason for coredump is known, but I do not know how to solve it gracefully
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2018-12-05 3:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-116-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 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).