DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Richardson, Bruce" <bruce.richardson@intel.com>
To: Sharath <sharathjm.bharadwaj@gmail.com>,
	Vladimir Medvedkin <medvedkinv@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] checking packet drop at NIC
Date: Fri, 7 Feb 2014 09:13:42 +0000	[thread overview]
Message-ID: <59AF69C657FD0841A61C55336867B5B01A999A51@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <CAJ6BMtAjAv2MaskgoG3onKCJu3SnenmS_ac0_CHWR0FZs6qy5Q@mail.gmail.com>

The Intel DPDK does not at present support interrupts for dropped packets. Only support for link status change interrupts are supported at this time, but since the basics are there, it is possible with a bit of work to add handling for other interrupts if so needed.

Regards,
/Bruce

> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Sharath
> Sent: Friday, February 07, 2014 5:44 AM
> To: Vladimir Medvedkin
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] checking packet drop at NIC
> 
> hi all,
> can anyone please let me know about this ??
> 
> Tx,
> -SB
> 
> 
> On Thu, Feb 6, 2014 at 11:20 AM, Sharath
> <sharathjm.bharadwaj@gmail.com>wrote:
> 
> > hi Vladimir,
> >
> > I would like to know if there are any callback mechanism to detect
> > FIFO errors in NIC ?
> > could you please let me know.
> >
> > Tx
> > -SB
> >
> >
> > On Fri, Jan 31, 2014 at 12:56 PM, Sharath
> <sharathjm.bharadwaj@gmail.com>wrote:
> >
> >> thank you Vladimir.
> >>
> >>
> >> On Fri, Jan 31, 2014 at 12:36 PM, Vladimir Medvedkin <
> >> medvedkinv@gmail.com> wrote:
> >>
> >>> Hi Sharath,
> >>>
> >>> In DPDK interrupts are disabled to eliminate the performance overhead.
> >>> Interrupts used only for link status change. So you can poll
> >>> rte_eth_stats_get and check struct rte_eth_stats for errors.
> >>>
> >>> Regards,
> >>> Vladimir
> >>>
> >>>
> >>>
> >>> 2014-01-31 Sharath <sharathjm.bharadwaj@gmail.com>
> >>>
> >>> Hi Daniel & all,
> >>>>
> >>>> can anyone please let me know about this.
> >>>>
> >>>> Tx
> >>>> -SB
> >>>>
> >>>>
> >>>> On Thu, Jan 30, 2014 at 4:50 PM, Sharath
> >>>> <sharathjm.bharadwaj@gmail.com
> >>>> >wrote:
> >>>>
> >>>> > 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-02-07  9:12 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
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 [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=59AF69C657FD0841A61C55336867B5B01A999A51@IRSMSX103.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=medvedkinv@gmail.com \
    --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).