From: Bruce Richardson <bruce.richardson@intel.com>
To: Kamaraj P <pkamaraj@gmail.com>
Cc: dev <dev@dpdk.org>,
Stephen Hemminger <stephen@networkplumber.org>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>
Subject: Re: DPDK RX Ring number dump
Date: Mon, 12 Dec 2022 10:36:56 +0000 [thread overview]
Message-ID: <Y5cESLO7xZi+d4Ii@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <CAG8PAapUJGta-RE+_xqEGUBco=cAEzsv+Yb5rUhqkT7Qc__DTg@mail.gmail.com>
On Mon, Dec 12, 2022 at 10:29:58AM +0530, Kamaraj P wrote:
> Hello All,
> We have an application where we need to dump the received packet rx
> ring number from the queue.
> Can anyone share the DPDK api to dump the rx ringnumber for the packet
> which we received (debug and troubleshoot)?
> Thanks,
> Kamaraj
Hi,
this information is not preserved in the DPDK mbuf structure, so is lost
after the call to rx-burst. The DPDK port field stores the port number on
return from rx_burst, but your app could look to reuse this field to store
the queue number also. For example, if you have only a few input ports, you
could encode the port number in the high bits of the "port" field, and
store the rx queue in the lower bits. This could be done as an rx-callback
if you want to avoid adjusting your app following each and every rx-burst
call.
/Bruce
next prev parent reply other threads:[~2022-12-12 10:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 4:59 Kamaraj P
2022-12-12 10:36 ` Bruce Richardson [this message]
2022-12-12 10:45 ` Kamaraj P
2022-12-12 11:03 ` Bruce Richardson
2022-12-12 16:31 ` Stephen Hemminger
2022-12-13 7:31 ` Kamaraj P
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=Y5cESLO7xZi+d4Ii@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=pkamaraj@gmail.com \
--cc=stephen@networkplumber.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).