DPDK usage discussions
 help / color / mirror / Atom feed
From: "Avinash ." <avinash.182cs009@nitk.edu.in>
To: users@dpdk.org
Cc: Gokul Bargaje <gokulbargaje.182009@nitk.edu.in>,
	 "Mohit P. Tahiliani" <tahiliani@nitk.edu.in>
Subject: [dpdk-users] DPDK Enqueue Pipeline
Date: Wed, 26 Feb 2020 16:08:17 +0530	[thread overview]
Message-ID: <CAONq4HZLkhh3ddYVjquGK519862tB5-=0FypG=GF1Kxm_81Ltw@mail.gmail.com> (raw)

Hi all,
The DPDK QoS scheduler has a 4-stage pipeline for enqueuing the packets.
This is used for hiding the latency of prefetching the data structures.
Why is there no pipeline for dequeuing the packets?
How does the dequeue function maintain the state of a packet? In other
words, if I want to backtrace the packet that is dequeued to get the info
of what was the traffic class and from which queue the packet was dequeued.
Is there any way to get this.

Thanks,
Avinash.

             reply	other threads:[~2020-02-26 10:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-26 10:38 Avinash . [this message]
2020-02-26 15:25 ` Stephen Hemminger
2020-02-27 10:14   ` Archit Pandey

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='CAONq4HZLkhh3ddYVjquGK519862tB5-=0FypG=GF1Kxm_81Ltw@mail.gmail.com' \
    --to=avinash.182cs009@nitk.edu.in \
    --cc=gokulbargaje.182009@nitk.edu.in \
    --cc=tahiliani@nitk.edu.in \
    --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).