All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Anjali Kulkarni <anjali@juniper.net>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: Debugging SR-IOV related packet flow problem with DPDK
Date: Tue, 16 Jun 2015 20:22:52 +0000	[thread overview]
Message-ID: <D1A5D38F.F491%anjali@juniper.net> (raw)
In-Reply-To: <D1A59829.F3D4%anjali@juniper.net>

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?

Anjali

From: Microsoft Office User <sumerj@juniper.net<mailto:sumerj@juniper.net>>
Date: Tuesday, June 16, 2015 at 9:10 AM
To: "dev@dpdk.org<mailto:dev@dpdk.org>" <dev@dpdk.org<mailto:dev@dpdk.org>>, Microsoft Office User <sumerj@juniper.net<mailto:sumerj@juniper.net>>
Cc: Microsoft Office User <sumerj@juniper.net<mailto:sumerj@juniper.net>>
Subject: Re: Debugging SR-IOV related packet flow problem with DPDK

Pls keep me on cc for response. Thanks!!

Hi,

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)?

Thanks
Anjali

  reply	other threads:[~2015-06-16 20:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-16 12:33 Debugging SR-IOV related packet flow problem with DPDK Anjali Kulkarni
2015-06-16 16:09 ` Anjali Kulkarni
2015-06-16 20:22   ` Anjali Kulkarni [this message]
2015-06-16 20:52     ` Thomas Monjalon
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=D1A5D38F.F491%anjali@juniper.net \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.