From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-bk0-x229.google.com (mail-bk0-x229.google.com [IPv6:2a00:1450:4008:c01::229]) by dpdk.org (Postfix) with ESMTP id 5E58D594F for ; Thu, 6 Feb 2014 06:49:27 +0100 (CET) Received: by mail-bk0-f41.google.com with SMTP id na10so503375bkb.14 for ; Wed, 05 Feb 2014 21:50:48 -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=RU0BUiKuV2otO5xKoAHFLhLiUxckKldv9iCa32t8SJs=; b=fQjaW3BbWGq9ZphjFCLNb1gHSPsnlK2CrBHiEepw//PL35d3DwFDOWVKpTvAjdjjL6 GxtRiufVX2+/XkZVT+XA/M9ZoFXlt8aroBg276Qn4sG4H9R63pYWpAsSYcBIlfZhnE2M w1llH0Gah+WykL3MHfRPU+eLAa6f4stYgAdNduOm3LuqFE5A3EJv9wrQ8L/zK+VL7liS mysrKSEHpyTQDsPGtKY9Fs6JQ+2SLJqnD5Fi6TKM/opL6cW8M0EGWAPBNhZgd978QyuU nUSRRLwfKuf3WhuJ0lPc0JJTSf/IIMaR3jJpNL1vjyy51JwKv4zswJRRVZP/8VOutiuz 02sA== MIME-Version: 1.0 X-Received: by 10.204.101.68 with SMTP id b4mr3739822bko.20.1391665848154; Wed, 05 Feb 2014 21:50:48 -0800 (PST) Received: by 10.204.197.208 with HTTP; Wed, 5 Feb 2014 21:50:48 -0800 (PST) In-Reply-To: References: Date: Thu, 6 Feb 2014 11:20:48 +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: Thu, 06 Feb 2014 05:49:27 -0000 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 > 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 >>> >>>> >>> >>> >>> >>> >>> > >>> >> >> >