From: Lokesh Chakka <lvenkatakumarchakka@gmail.com>
To: users <users@dpdk.org>
Subject: rte_eth_tx_burst giving error
Date: Mon, 16 Dec 2024 17:26:20 +0530 [thread overview]
Message-ID: <CACh--sjqPjGM+-h5jQsJ_U_V15HXJu+xUu_F8uv_JL2B16CTYQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 748 bytes --]
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.
[-- Attachment #2: Type: text/html, Size: 1339 bytes --]
next reply other threads:[~2024-12-16 11:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 11:56 Lokesh Chakka [this message]
2024-12-16 16:58 ` Stephen Hemminger
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=CACh--sjqPjGM+-h5jQsJ_U_V15HXJu+xUu_F8uv_JL2B16CTYQ@mail.gmail.com \
--to=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).