DPDK usage discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Lokesh Chakka <lvenkatakumarchakka@gmail.com>
Cc: users <users@dpdk.org>
Subject: Re: rte_eth_tx_burst giving error
Date: Mon, 16 Dec 2024 08:58:41 -0800	[thread overview]
Message-ID: <20241216085841.16efa701@hermes.local> (raw)
In-Reply-To: <CACh--sjqPjGM+-h5jQsJ_U_V15HXJu+xUu_F8uv_JL2B16CTYQ@mail.gmail.com>

On Mon, 16 Dec 2024 17:26:20 +0530
Lokesh Chakka <lvenkatakumarchakka@gmail.com> wrote:

> hi,
> 
> please refer to the small piece of code at
> 
> https://bitbucket.org/chakkadotlokesh/learning_dpdk/src/main/pmd_tx.c
> 
> This code is functioning fine in dpdk 23.11
> But giving following error in 24.11
> 
> ================================================================
> Thread 106 received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0x7fa8d8ff1640 (LWP 14264)]
> 0x000000000041a4de in rte_eth_tx_burst (port_id=0, queue_id=0,
> tx_pkts=0x17f8b3180, nb_pkts=4096) at /usr/include/dpdk/rte_ethdev.h:6425
> 6425     * callback is called with the unsent packets as a parameter. If no
> callback
> ================================================================
> 
> Can someone help me understand what might be wrong?
> 
> 
> Thanks & Regards
> --
> Lokesh Chakka.

Do a debug build (with -Dbuildtype=debug) and run it under gdb.
You might also want to enable ETHDEV_DEBUG and MBUF_DEBUG in rte_config.h

      reply	other threads:[~2024-12-16 16:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-16 11:56 Lokesh Chakka
2024-12-16 16:58 ` Stephen Hemminger [this message]

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=20241216085841.16efa701@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=lvenkatakumarchakka@gmail.com \
    --cc=users@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).