From: Archit Pandey <architpandeynitk@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "Avinash ." <avinash.182cs009@nitk.edu.in>,
users@dpdk.org, Gokul Bargaje <gokulbargaje.182009@nitk.edu.in>,
"Mohit P. Tahiliani" <tahiliani@nitk.edu.in>
Subject: Re: [dpdk-users] DPDK Enqueue Pipeline
Date: Thu, 27 Feb 2020 15:44:50 +0530 [thread overview]
Message-ID: <CANtWViO-7kAsVGR3BuXqOAPpx_EaqtRmYKB5JgkrQmE4sZV19w@mail.gmail.com> (raw)
In-Reply-To: <20200226072518.3496f5ee@hermes.lan>
In that case, since the packets have been prefetched on enqueue,
would it be necessary to prefetch the packets again upon dequeue?
As an example, DPDK's QoS scheduler only prefetches on enqueue
(using a packet pipeline to hide prefetch latency).
On Wed, Feb 26, 2020 at 8:55 PM Stephen Hemminger <
stephen@networkplumber.org> wrote:
> On Wed, 26 Feb 2020 16:08:17 +0530
> "Avinash ." <avinash.182cs009@nitk.edu.in> wrote:
>
> > 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.
>
> Prefetching after receive burst is the responsibility of the application.
> You can't prefetch until the data arrives, and the amount and policy
> for prefetch depends on the timing of the application.
>
> There simple examples in DPDK and more complex in how FD.io VPP does it.
>
--
Archit Pandey
Senior Year B.Tech.
Department of Computer Science and Engineering
National Institute of Technology Karnataka
Surathkal, India
prev parent reply other threads:[~2020-02-27 10:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 10:38 Avinash .
2020-02-26 15:25 ` Stephen Hemminger
2020-02-27 10:14 ` Archit Pandey [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=CANtWViO-7kAsVGR3BuXqOAPpx_EaqtRmYKB5JgkrQmE4sZV19w@mail.gmail.com \
--to=architpandeynitk@gmail.com \
--cc=avinash.182cs009@nitk.edu.in \
--cc=gokulbargaje.182009@nitk.edu.in \
--cc=stephen@networkplumber.org \
--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).