From: "Wiles, Keith" <keith.wiles@intel.com>
To: SAKTHIVEL ANAND S <anand.sa88@gmail.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] memory tracker in PMD level
Date: Tue, 31 May 2016 15:05:27 +0000 [thread overview]
Message-ID: <3A97B4DA-4383-46F3-9DF8-AFA5E868DACD@intel.com> (raw)
In-Reply-To: <CAOP5GAxgAt2B7W_H1QSHomO44Cn1drnpJQu50rWAifLzSAxDjA@mail.gmail.com>
>Hi
>
>How can we track the packet drops in the PMD level, when receiving rings is
>full or by some other means.
>
>Lets assume my processing speed is less than receiving line rate so PMD
>rings are over run and incoming packets are getting dropped. how should i
>track this issue(status of mbufs and dropping packets counts in PMD). Is
>there any APIs or any tool available? is libtrace will help here?
I sent this information offline, but sending here for others:
Please have a look at the Docs in the area of rte_eth_stats_get() https://readthedocs.org/projects/dpdk/
>
>any help would be much appreciated.
>
>--
>Thanks
>Sakthivel S OM
>
prev parent reply other threads:[~2016-05-31 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 14:35 SAKTHIVEL ANAND S
2016-05-31 14:42 ` Wiles, Keith
[not found] ` <CAOP5GAzAsGvZfiU=iScotEvj-uDL_9stuPZ5a1JN8rjXXv9Tug@mail.gmail.com>
[not found] ` <014B49F6-8810-4975-8CE5-967B4299B14E@intel.com>
[not found] ` <CAOP5GAzTGWefN6PSK+Ff7k_Aa2da4+3gCuu420BPKY56VvBXpg@mail.gmail.com>
[not found] ` <CAOP5GAxCp-4z2crmCxtKTGTWe-90==M_Fia92riNzxrCrL8iEQ@mail.gmail.com>
[not found] ` <68349471-4A9C-46EB-90EA-3FF67C28F0F5@intel.com>
[not found] ` <9D6F629A-2B3E-4E44-8ED3-83C231C421A0@intel.com>
[not found] ` <CAOP5GAwHJ9N6XPQDEBRYn4HyioGRw18ewT-8nh=zoakSrSvzbQ@mail.gmail.com>
2016-06-02 7:10 ` SAKTHIVEL ANAND S
2016-05-31 15:05 ` Wiles, Keith [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=3A97B4DA-4383-46F3-9DF8-AFA5E868DACD@intel.com \
--to=keith.wiles@intel.com \
--cc=anand.sa88@gmail.com \
--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).