DPDK patches and discussions
 help / color / mirror / Atom feed
From: Sharath <sharathjm.bharadwaj@gmail.com>
To: Daniel Kaminsky <daniel.kaminsky@infinitelocality.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] checking packet drop at NIC
Date: Thu, 30 Jan 2014 16:50:45 +0530	[thread overview]
Message-ID: <CAJ6BMtC-HZzje_ipqWYUAH_miYeFm+cqtb-gwO_XAewzExo2SA@mail.gmail.com> (raw)
In-Reply-To: <CAJ6BMtAF7WT5A+R2xLkHo_eAZZzqqFArkijcp=9S49Z-zYvNLw@mail.gmail.com>

hi!

are there any interrupts which are raised by DPDK, for the fifo errors.

please let me know, where can I find the details and how to handle such
interrupts ?

Tx
-SB


On Thu, Jan 30, 2014 at 2:30 PM, Sharath <sharathjm.bharadwaj@gmail.com>wrote:

> Thanks Daniel !
> Let me check it out . . .
> On Jan 29, 2014 8:54 PM, "Daniel Kaminsky" <
> daniel.kaminsky@infinitelocality.com> wrote:
>
>> 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
>>>
>>
>>

  reply	other threads:[~2014-01-30 11:19 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
2014-01-30  9:00   ` Sharath
2014-01-30 11:20     ` Sharath [this message]
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=CAJ6BMtC-HZzje_ipqWYUAH_miYeFm+cqtb-gwO_XAewzExo2SA@mail.gmail.com \
    --to=sharathjm.bharadwaj@gmail.com \
    --cc=daniel.kaminsky@infinitelocality.com \
    --cc=dev@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).