DPDK patches and discussions
 help / color / mirror / Atom feed
From: Kamaraj P <pkamaraj@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Bruce Richardson <bruce.richardson@intel.com>, dev <dev@dpdk.org>,
	 "Burakov, Anatoly" <anatoly.burakov@intel.com>
Subject: Re: DPDK RX Ring number dump
Date: Tue, 13 Dec 2022 13:01:44 +0530	[thread overview]
Message-ID: <CAG8PAaomwE4gP+PcOhbRqYMrQfFfGngOBYaD+scyhjK8AENHUA@mail.gmail.com> (raw)
In-Reply-To: <20221212083125.490ef9d2@hermes.local>

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

Thanks Stephen,.
As Bruce suggested earlier we cannot get ringnumber from the queue(attached
to the port) after rx_burst call.

Thanks,
Kamaraj


On Mon, 12 Dec 2022, 10:01 pm Stephen Hemminger, <stephen@networkplumber.org>
wrote:

> On Mon, 12 Dec 2022 11:03:03 +0000
> Bruce Richardson <bruce.richardson@intel.com> wrote:
>
> > On Mon, Dec 12, 2022 at 04:15:04PM +0530, Kamaraj P wrote:
> > >    Thanks. Is there any teatpmd application has this logic to dump
> these
> > >    info whenever we received the packet.
> > >    Thanks,
> > >    Kamaraj
> > >
> > Sorry, no. No example application has the logic to do this.
>
> Since the DPDK uses a pull model, the receive queue is known
> when calling rx_burst().
>

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

      reply	other threads:[~2022-12-13  7:31 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
2022-12-12 11:03     ` Bruce Richardson
2022-12-12 16:31       ` Stephen Hemminger
2022-12-13  7:31         ` Kamaraj P [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=CAG8PAaomwE4gP+PcOhbRqYMrQfFfGngOBYaD+scyhjK8AENHUA@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).