From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-bk0-x236.google.com (mail-bk0-x236.google.com [IPv6:2a00:1450:4008:c01::236]) by dpdk.org (Postfix) with ESMTP id 86660DE3 for ; Fri, 7 Feb 2014 06:42:16 +0100 (CET) Received: by mail-bk0-f54.google.com with SMTP id u14so927469bkz.13 for ; Thu, 06 Feb 2014 21:43:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=KKiR3M+KA3pD3sky/1mKUInaAA4EMIfvV2h3XPebpSc=; b=HkgLlnNraeo+yH5Jgj7+9DQZoiVg+ijucVTp20Cf3dUKhWCknVCkRXyyLl+rY5uNZ3 Y0vzbky7uYYTeZdWNPE4V5BFPyDt+5OLOEiPiUZIfJ8j8L8M6A3XSuTBaOz4ZqV1zEGw gx7mKLgCRvzOghaZTucHW4c+tJiwrl5il+GLcAPdWCdG2MoE4PkhvF0IYTMMHnmBVEhH Jn4nc7dg4GcebN1sl85UkgZETaHG+CvcKXMcfQEplJxxggoyuiBS7XSFW39j4r8y7jg0 ixiZgtWcG/i4kBpOVb8rVJYjwvggiPvvbiq/JqZROpzfOWBZSz9rtuaJP8h2GBH0ZJNA cQTg== MIME-Version: 1.0 X-Received: by 10.205.41.202 with SMTP id tv10mr9772bkb.41.1391751817492; Thu, 06 Feb 2014 21:43:37 -0800 (PST) Received: by 10.204.197.208 with HTTP; Thu, 6 Feb 2014 21:43:37 -0800 (PST) In-Reply-To: References: Date: Fri, 7 Feb 2014 11:13:37 +0530 Message-ID: From: Sharath To: Vladimir Medvedkin Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] checking packet drop at NIC X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Feb 2014 05:42:17 -0000 hi all, can anyone please let me know about this ?? Tx, -SB On Thu, Feb 6, 2014 at 11:20 AM, Sharath 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 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 >>> >>> Hi Daniel & all, >>>> >>>> can anyone please let me know about this. >>>> >>>> Tx >>>> -SB >>>> >>>> >>>> On Thu, Jan 30, 2014 at 4:50 PM, Sharath >>> >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 >>>> >>>> >>>> >>> >>>> >>> >>>> > >>>> >>> >>> >> >