DPDK patches and discussions
 help / color / mirror / Atom feed
From: Kamaraj P <pkamaraj@gmail.com>
To: Bruce Richardson <bruce.richardson@intel.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 16:15:04 +0530	[thread overview]
Message-ID: <CAG8PAaqG7gixBcUfb3tWFtJug2wdLoKYS-dt1EzvbyirkpRd7w@mail.gmail.com> (raw)
In-Reply-To: <Y5cESLO7xZi+d4Ii@bricha3-MOBL.ger.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]

Thanks. Is there any teatpmd application has this logic to dump these info
whenever we received the packet.

Thanks,
Kamaraj

On Mon, 12 Dec 2022, 4:07 pm Bruce Richardson, <bruce.richardson@intel.com>
wrote:

> 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
>

[-- Attachment #2: Type: text/html, Size: 1567 bytes --]

  reply	other threads:[~2022-12-12 10:45 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
2022-12-12 10:45   ` Kamaraj P [this message]
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=CAG8PAaqG7gixBcUfb3tWFtJug2wdLoKYS-dt1EzvbyirkpRd7w@mail.gmail.com \
    --to=pkamaraj@gmail.com \
    --cc=anatoly.burakov@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --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).