From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-la0-x236.google.com (mail-la0-x236.google.com [IPv6:2a00:1450:4010:c03::236]) by dpdk.org (Postfix) with ESMTP id E687158EB for ; Fri, 31 Jan 2014 08:04:57 +0100 (CET) Received: by mail-la0-f54.google.com with SMTP id y1so3260266lam.27 for ; Thu, 30 Jan 2014 23:06:16 -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=PK0qt62VGpXBKkFVMU7A1PekEkeZ6OxO8IN3mwRjuNg=; b=d6g6CQnCt9eYwLLU6XLq6qseh+zmxzz5+SIvyU7PIdc0OJV3nPTVqwAo9AhhG5nnmR LGXmKmyqji9L5AqT+b+aVBPSEAXxKBeoQ57/lHwIHbL0qDcwatPLvUP+jh/mLb/7Y/Tw 7Vf4DYsYJBM/DgnVrzycQEqQm5WyOMonlZcSIgM1NGlk5qWAfg1Ln926C4e/XsogNOQc Yr8TurZtxYHixg9bls6MWpkDlp2SPm9xY1aF3bLTkBGYicV+kNV3bBZIu/VcDPh4s9Lq jjY8xgz8gEXEbIbmPg6MZIfvv4kMnZ4K8FK/qQkV9ZE5uc0KQPm6GNx0MmFOjIAjtYnS QWmw== MIME-Version: 1.0 X-Received: by 10.112.154.202 with SMTP id vq10mr11976667lbb.3.1391151976627; Thu, 30 Jan 2014 23:06:16 -0800 (PST) Received: by 10.114.1.232 with HTTP; Thu, 30 Jan 2014 23:06:16 -0800 (PST) In-Reply-To: References: Date: Fri, 31 Jan 2014 11:06:16 +0400 Message-ID: From: Vladimir Medvedkin To: Sharath 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, 31 Jan 2014 07:04:58 -0000 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 >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 > >>>> > >>> > >>> > > >