DPDK usage discussions
 help / color / Atom feed
* [dpdk-users] DPDK issue with XL710/X710
@ 2019-06-22  8:17 Inder
  0 siblings, 0 replies; only message in thread
From: Inder @ 2019-06-22  8:17 UTC (permalink / raw)
  To: users, dev

Hi Team,

We are facing an issue with running DPDK on NIC XL710/X710 with SRIOV based
configuration. while configuring 4 cores in system we get an issue that
DPDK get stuck while polling the packets from rings.

here is the stack below

#0  0x00007f614242acae in common_ring_mc_dequeue (mp=0x7f565d6c3d80,
obj_table=0x7f565d6c9ed0, n=544) at
/mnt/utkarsh/git_repos/190619_clone/mn-vpp/fastpath/build-vpp-mav/vpp/build-root/build-vpp-native/dpdk/dpdk-18.05/drivers/mempool/ring/rte_mempool_ring.c:30

#1  0x00007f61425a06d1 in rte_mempool_ops_dequeue_bulk (n=544,
obj_table=<optimized out>, mp=0x7f565d6c3d80) at
/mnt/utkarsh/git_repos/190619_clone/mn-vpp/fastpath/build-vpp-mav/vpp/build-root/build-vpp-native/dpdk/dpdk-18.05/x86_64-native-linuxapp-gcc/include/rte_mempool.h:679

#2  __mempool_generic_get (cache=0x7f565d6c9ec0, n=32,
obj_table=0x7f565d61b4c0, mp=0x7f565d6c3d80) at
/mnt/utkarsh/git_repos/190619_clone/mn-vpp/fastpath/build-vpp-mav/vpp/build-root/build-vpp-native/dpdk/dpdk-18.05/x86_64-native-linuxapp-gcc/include/rte_mempool.h:1495

#3  rte_mempool_generic_get (cache=0x7f565d6c9ec0, n=32,
obj_table=0x7f565d61b4c0, mp=0x7f565d6c3d80) at
/mnt/utkarsh/git_repos/190619_clone/mn-vpp/fastpath/build-vpp-mav/vpp/build-root/build-vpp-native/dpdk/dpdk-18.05/x86_64-native-linuxapp-gcc/include/rte_mempool.h:1558

#4  rte_mempool_get_bulk (n=32, obj_table=0x7f565d61b4c0,
mp=0x7f565d6c3d80) at
/mnt/utkarsh/git_repos/190619_clone/mn-vpp/fastpath/build-vpp-mav/vpp/build-root/build-vpp-native/dpdk/dpdk-18.05/x86_64-native-linuxapp-gcc/include/rte_mempool.h:1591

#5  i40e_rxq_rearm (rxq=0x7f565db36900) at
/mnt/utkarsh/git_repos/190619_clone/mn-vpp/fastpath/build-vpp-mav/vpp/build-root/build-vpp-native/dpdk/dpdk-18.05/drivers/net/i40e/i40e_rxtx_vec_avx2.c:61

#6  _recv_raw_pkts_vec_avx2 (split_packet=0x7f62d8130c80 "", nb_pkts=32,
rx_pkts=0x7f62d7ac6940, rxq=0x7f565db36900) at
/mnt/utkarsh/git_repos/190619_clone/mn-vpp/fastpath/build-vpp-mav/vpp/build-root/build-vpp-native/dpdk/dpdk-18.05/drivers/net/i40e/i40e_rxtx_vec_avx2.c:192

#7  i40e_recv_scattered_burst_vec_avx2 (rx_queue=rx_queue@entry=0x7f565db36900,
rx_pkts=rx_pkts@entry=0x7f62d7ac6940, nb_pkts=nb_pkts@entry=32) at
/mnt/utkarsh/git_repos/190619_clone/mn-vpp/fastpath/build-vpp-mav/vpp/build-root/build-vpp-native/dpdk/dpdk-18.05/drivers/net/i40e/i40e_rxtx_vec_avx2.c:600

#8  0x00007f61425a256b in i40e_recv_scattered_pkts_vec_avx2
(rx_queue=0x7f565db36900, rx_pkts=0x7f62d7ac6940, nb_pkts=256) at
/mnt/utkarsh/git_repos/190619_clone/mn-vpp/fastpath/build-vpp-mav/vpp/build-root/build-vpp-native/dpdk/dpdk-18.05/drivers/net/i40e/i40e_rxtx_vec_avx2.c:639

#9  0x00007f6142376ea4 in rte_eth_rx_burst (nb_pkts=256,
rx_pkts=0x7f62d7ac6940, queue_id=1, port_id=0) at
/home/utkarsh/git_repos/190619_clone/mn-vpp/fastpath/build-vpp-mav/vpp/build-root/install-vpp-native/dpdk/include/dpdk/rte_ethdev.h:3844

#10 dpdk_device_input (queue_id=1, thread_index=<optimized out>,
node=0x7f62d867f480, xd=0x7f62d7b11580, dm=<optimized out>,
vm=0x7f62d7a1ed40) at
/mnt/utkarsh/git_repos/190619_clone/mn-vpp/fastpath/build-vpp-mav/vpp/build-data/../src/plugins/dpdk/device/node.c:459

#11 dpdk_input_node_fn (vm=<optimized out>, node=<optimized out>,
f=<optimized out>) at
/mnt/utkarsh/git_repos/190619_clone/mn-vpp/fastpath/build-vpp-mav/vpp/build-data/../src/plugins/dpdk/device/node.c:640

#12 0x00007f6945d3a61b in dispatch_node (last_time_stamp=345121778085630,
frame=0x0, dispatch_state=VLIB_NODE_STATE_POLLING,
type=VLIB_NODE_TYPE_INPUT, node=0x7f62d867f480, vm=0x7f62d7a1ed40) at
/mnt/utkarsh/git_repos/190619_clone/mn-vpp/fastpath/build-vpp-mav/vpp/build-data/../src/vlib/main.c:988

#13 vlib_main_or_worker_loop (is_main=0, vm=0x7f62d7a1ed40) at
/mnt/utkarsh/git_repos/190619_clone/mn-vpp/fastpath/build-vpp-mav/vpp/build-data/../src/vlib/main.c:1507

#14 vlib_worker_loop (vm=0x7f62d7a1ed40) at
/mnt/utkarsh/git_repos/190619_clone/mn-vpp/fastpath/build-vpp-mav/vpp/build-data/../src/vlib/main.c:1641

#15 0x00007f694485b418 in clib_calljmp () at
/mnt/utkarsh/git_repos/190619_clone/mn-vpp/fastpath/build-vpp-mav/vpp/build-data/../src/vppinfra/longjmp.S:110

#16 0x00007f49dc7fcdc0 in ?? ()

#17 0x00007f61423c892d in eal_thread_loop (arg=<optimized out>) at
/mnt/utkarsh/git_repos/190619_clone/mn-vpp/fastpath/build-vpp-mav/vpp/build-root/build-vpp-native/dpdk/dpdk-18.05/lib/librte_eal/linuxapp/eal/eal_thread.c:153

#18 0x0260000000856403 in ?? ()

#19 0x0000000000000000 in ?? ()


regards

Inder

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, back to index

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-06-22  8:17 [dpdk-users] DPDK issue with XL710/X710 Inder

DPDK usage discussions

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ http://inbox.dpdk.org/users \
		users@dpdk.org
	public-inbox-index users


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.users


AGPL code for this site: git clone https://public-inbox.org/ public-inbox