From: "Pathak, Pravin" <pravin.pathak@intel.com>
To: Lokesh Chakka <lvenkatakumarchakka@gmail.com>,
Bing Zhao <bingz@nvidia.com>
Cc: users <users@dpdk.org>
Subject: RE: unable to capture packets
Date: Mon, 7 Oct 2024 16:02:37 +0000 [thread overview]
Message-ID: <BL1PR11MB546184E13F04F6F94FFD793BF47D2@BL1PR11MB5461.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CACh--sgiUuc5M=xD1dMEL9vunPe6Jnj=SEFPmoUOL_xYdssNQg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1588 bytes --]
I hope accidentally num_of_pkts_per_queue is not zero.
Pravin
From: Lokesh Chakka <lvenkatakumarchakka@gmail.com>
Sent: Monday, October 7, 2024 11:36 AM
To: Bing Zhao <bingz@nvidia.com>
Cc: users <users@dpdk.org>
Subject: Re: unable to capture packets
I've tried TX. It's working fine.
I'm sure problem is only with my code.
On Mon, 7 Oct, 2024, 20:52 Bing Zhao, <bingz@nvidia.com<mailto:bingz@nvidia.com>> wrote:
Which NIC are you using?
Have you tried dpdk-testpmd or l2fwd on your setup to check if the packet can be sent and received correctly?
BR. Bing
From: Lokesh Chakka <lvenkatakumarchakka@gmail.com<mailto:lvenkatakumarchakka@gmail.com>>
Sent: Monday, October 7, 2024 9:52 PM
To: users <users@dpdk.org<mailto:users@dpdk.org>>
Subject: unable to capture packets
External email: Use caution opening links or attachments
hello,
I'm trying to capture packets using the following piece of code :
==========================================================
struct rte_eth_rxconf rxq_conf = dev_info.default_rxconf;
rxq_conf.offloads = port_conf.rxmode.offloads;
rte_eth_rx_queue_setup( 0, 0, num_of_pkts_per_queue, (unsigned int)sock, &rxq_conf, mem_pool );
rte_eth_dev_start( 0 );
while( 1 )
{
num_of_pkts_rcvd = rte_eth_rx_burst( 0, 0, mbuf, num_of_pkts_per_queue );
fprintf( stderr, "num_of_pkts_rcvd: %u\n", num_of_pkts_rcvd );
}
==========================================================
It's always printing num_of_pkts_rcvd as 0.
Can someone help me understand what the issue is ....
Thanks & Regards
--
Lokesh Chakka.
[-- Attachment #2: Type: text/html, Size: 7673 bytes --]
next prev parent reply other threads:[~2024-10-07 16:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 13:52 Lokesh Chakka
2024-10-07 15:21 ` Bing Zhao
2024-10-07 15:34 ` Stephen Hemminger
2024-10-07 15:36 ` Lokesh Chakka
2024-10-07 16:02 ` Pathak, Pravin [this message]
2024-10-07 22:10 ` Lokesh Chakka
2024-10-08 0:23 ` Stephen Hemminger
2024-10-09 12:15 ` Lokesh Chakka
2024-10-09 13:27 ` Van Haaren, Harry
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=BL1PR11MB546184E13F04F6F94FFD793BF47D2@BL1PR11MB5461.namprd11.prod.outlook.com \
--to=pravin.pathak@intel.com \
--cc=bingz@nvidia.com \
--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).