DPDK patches and discussions
 help / color / mirror / Atom feed
From: Gokul Bargaje <gokulbargaje.182009@nitk.edu.in>
To: dev@dpdk.org, users@dpdk.org
Subject: [dpdk-dev] Fwd: How to check the packets dropped by RED in DPDK?
Date: Mon, 6 Jan 2020 15:58:43 +0530	[thread overview]
Message-ID: <CAH1-=xhoxQMtP6w7D1Ege5OLRisDTxfeea4tJ9ssRtkUWkYowA@mail.gmail.com> (raw)
In-Reply-To: <CAH1-=xippBMVe-kP2CY-hR3_sqsvh5Q-6yqfuYFz4PyDBn50dQ@mail.gmail.com>

Correcting the 'packet drop' mentioned in the previous mail.

Hi All,

I am running the qos_sched sample application to see the RED packet drop. I
am generating the traffic and sending the traffic via qos_sched
application. As a result,
1. The application is showing the packet drop which is so high as shown in
the below figure.
2. How to determine that the packets are dropped by the RED or TAIL drop
method?

Following is the output I am getting from an application on every second.

*_______________________________________________*







*RX port 1: rx: 22954 err: 0  no_mbuf: 0TX port 0: tx: 1088    err:
0-------------+----------------+----------------+                |
 received    |   dropped
|-------------+----------------+----------------+     RX       |     20476
   |          0         | QOS+TX |     20476    |     19383      |
pps:1093--------------+---------------+-----------------+*
_______________________________________________
I have enabled RED from the configuration file by enabling following flags.

*CONFIG_RTE_SCHED_RED=y*
*CONFIG_RTE_SCHED_COLLECT_STATS=y*

Please do help if you can.

Thank you,
Gokul

      reply	other threads:[~2020-01-06 10:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.40583.1578305599.7586.users@dpdk.org>
2020-01-06 10:24 ` Gokul Bargaje
2020-01-06 10:28   ` Gokul Bargaje [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='CAH1-=xhoxQMtP6w7D1Ege5OLRisDTxfeea4tJ9ssRtkUWkYowA@mail.gmail.com' \
    --to=gokulbargaje.182009@nitk.edu.in \
    --cc=dev@dpdk.org \
    --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).