DPDK patches and discussions
 help / color / mirror / Atom feed
From: "bai bakari" <912873551@qq.com>
To: dev <dev@dpdk.org>
Subject: [dpdk-dev] TX offloads lead to Segmentation fault?
Date: Tue, 25 Dec 2018 19:43:53 +0800	[thread overview]
Message-ID: <tencent_D8D4BA207B42199CDD4AFE3ACC9E3B6DE808@qq.com> (raw)

Hi,


When I enable the Tx offloads capabilities, I get the segmentation fault.
The backtrace like this:
lcore_main_loop
	--> main_loop_tx
		--> rte_eth_tx_burst
			--> eth_igb_xmit_pkts
				--> rte_pktmbuf_free_seg
					--> rte_pktmbuf_prefree_seg
						--> rte_pktmbuf_detach
							--> __rte_pktmbuf_free_extbuf
								--> rte_mbuf_ext_refcnt_update
									--> rte_mbuf_ext_refcnt_read
										--> rte_atomic16_read
											return v->cnt;



And I set Tx offloads like this:
.txmode = {
        .mq_mode = ETH_MQ_TX_NONE,
        .offloads = DEV_TX_OFFLOAD_IPV4_CKSUM | \
                    DEV_TX_OFFLOAD_TCP_CKSUM | \
                    DEV_TX_OFFLOAD_UDP_CKSUM
    },



and set the m->ol_flags, l2_len, l3_len and l4_len.




Is there something I am missing? The NIC is Intel Corporation I350 Gigabit Network Connection(rev 01).


Thanks in advance.
bakari

                 reply	other threads:[~2018-12-25 11:43 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=tencent_D8D4BA207B42199CDD4AFE3ACC9E3B6DE808@qq.com \
    --to=912873551@qq.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).