From: Daniel Kaminsky <daniel.kaminsky@infinitelocality.com>
To: Sharath <sharathjm.bharadwaj@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] checking packet drop at NIC
Date: Wed, 29 Jan 2014 17:24:37 +0200 [thread overview]
Message-ID: <CA+8v-JyXuuEBs0yj=s0pec6hZ_N=AYiXBgK+5yUhXb-KhDqBgQ@mail.gmail.com> (raw)
In-Reply-To: <CAJ6BMtCtcsLQux5zT8h2Ah67CGXhGsdfXEC8U=37OqsdLtY6Ow@mail.gmail.com>
Hi Sharath,
Try rte_eth_stats_get, I think this should give you what you're looking for.
Regards,
Daniel
On Tue, Jan 28, 2014 at 7:29 AM, Sharath <sharathjm.bharadwaj@gmail.com>wrote:
> hi !
>
> can someone please tell me whether the DPDK provides any method to handle
> below
>
> a. account the packet drops at NIC level ? is there any interrupt raised by
> DPDK for the same ?
> b. to check fifo errors ?
> c. way to check rx and tx in sync
>
> Tx,
> -SB
>
next prev parent reply other threads:[~2014-01-29 15:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 5:29 Sharath
2014-01-29 15:24 ` Daniel Kaminsky [this message]
2014-01-30 9:00 ` Sharath
2014-01-30 11:20 ` Sharath
2014-01-31 6:05 ` Sharath
2014-01-31 7:06 ` Vladimir Medvedkin
2014-01-31 7:26 ` Sharath
2014-02-06 5:50 ` Sharath
2014-02-07 5:43 ` Sharath
2014-02-07 9:13 ` Richardson, Bruce
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='CA+8v-JyXuuEBs0yj=s0pec6hZ_N=AYiXBgK+5yUhXb-KhDqBgQ@mail.gmail.com' \
--to=daniel.kaminsky@infinitelocality.com \
--cc=dev@dpdk.org \
--cc=sharathjm.bharadwaj@gmail.com \
/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).