From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas.monjalon@6wind.com>
Received: from mail-wi0-f181.google.com (mail-wi0-f181.google.com
 [209.85.212.181]) by dpdk.org (Postfix) with ESMTP id F2347C34A
 for <dev@dpdk.org>; Tue, 16 Jun 2015 22:53:46 +0200 (CEST)
Received: by wiga1 with SMTP id a1so120022405wig.0
 for <dev@dpdk.org>; Tue, 16 Jun 2015 13:53:46 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:from:to:cc:subject:date:message-id:organization
 :user-agent:in-reply-to:references:mime-version
 :content-transfer-encoding:content-type;
 bh=4+dYUlAy8K4VhRkW69zqlZMlIjkee0cnUvNy3ntQj/U=;
 b=ZwP2FaIs7IJmL3atUU8wgwVIhKZ4HdTsYOtE+2HtpTKZ9TExckrLuIDc0QhNImKobt
 OqtmihEwhwYQg7L3MQWegB+Xiu+TN8a2TQN76gERxRhLmLkx3SrVJdD9sJ/G6X5V8xWb
 7DuOWo89gXsXU4419uaBAEvz0IMCIv2Xe/EEtZhOHDBRbpVyx0n1EVeCQi66J0xooVJS
 WfR6qqfgpuYhCowUHrT0x4k+CVwbM4oeVzSj3kQGHHW24bLHt02JOb6VjM88Geb5tyPm
 yxHMdOkG+y7kQCK0p2HyPVdN5mXqB1p+eHKoi9M8oRAbngsffOMOPWFL9cvCjBQqjgME
 YLcw==
X-Gm-Message-State: ALoCoQlUWeZE4I/ThO4Fy89vefF6jYpVZM9Q3WEjI2XDglXSNNC3WILC6y/meG3haJ+jpnN73kVU
X-Received: by 10.180.103.227 with SMTP id fz3mr10667073wib.45.1434488026889; 
 Tue, 16 Jun 2015 13:53:46 -0700 (PDT)
Received: from xps13.localnet (136-92-190-109.dsl.ovh.fr. [109.190.92.136])
 by mx.google.com with ESMTPSA id o6sm22563740wiz.24.2015.06.16.13.53.45
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Tue, 16 Jun 2015 13:53:45 -0700 (PDT)
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Anjali Kulkarni <anjali@juniper.net>
Date: Tue, 16 Jun 2015 22:52:46 +0200
Message-ID: <15776821.ucWqCiW9hh@xps13>
Organization: 6WIND
User-Agent: KMail/4.14.8 (Linux/4.0.4-2-ARCH; KDE/4.14.8; x86_64; ; )
In-Reply-To: <D1A5D38F.F491%anjali@juniper.net>
References: <D1A565DC.F3BF%anjali@juniper.net>
 <D1A59829.F3D4%anjali@juniper.net> <D1A5D38F.F491%anjali@juniper.net>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Debugging SR-IOV related packet flow problem with
	DPDK
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jun 2015 20:53:47 -0000

Hi,

That's third email in 8 hours for this question.
Do you plan to send an email every 4 hours?

It's really hard to help you without knowing which application you run?
in which VM? which VLAN configuration? etc

2015-06-16 20:22, Anjali Kulkarni:
> Hi,
> 
> Can someone please help with this? How can packet flow be traced on DPDK?
> Where are all the logs stored if we do enable the _DEBUG configs in
> config/ directory?

stdout or somewhere else if you configured logs in your app.

> Anjali
[...]
> I am observing that the SR-IOV enabled NIC does not increment any VF packet
> counters despite incoming packet flow. I have enabled some debug logs like
> CONFIG_RTE_LIBRTE_IXGBE_DEBUG_RX in config file.
> Can someone point me to where these logs are being printed so I can try to
> figure out where packets are being dropped? Or how can I debug DPDK packet
> flow related issues (are there any stats I can look at)?

Statistics can be requested through a dedicated ethdev API.