From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Anjali Kulkarni <anjali@juniper.net>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Debugging SR-IOV related packet flow problem with DPDK
Date: Tue, 16 Jun 2015 22:52:46 +0200 [thread overview]
Message-ID: <15776821.ucWqCiW9hh@xps13> (raw)
In-Reply-To: <D1A5D38F.F491%anjali@juniper.net>
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.
next prev parent reply other threads:[~2015-06-16 20:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 12:33 Anjali Kulkarni
2015-06-16 16:09 ` Anjali Kulkarni
2015-06-16 20:22 ` Anjali Kulkarni
2015-06-16 20:52 ` Thomas Monjalon [this message]
2015-06-16 21:08 ` Anjali Kulkarni
2015-06-17 10:52 ` Anjali Kulkarni
2015-06-17 15:16 ` Andrew Harvey (agh)
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=15776821.ucWqCiW9hh@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=anjali@juniper.net \
--cc=dev@dpdk.org \
/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).