DPDK patches and discussions
 help / color / mirror / Atom feed
From: Sambath Kumar Balasubramanian <sambath.balasubramanian@gmail.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Debugging igbvf_pmd
Date: Sat, 2 Nov 2013 15:56:29 -0700	[thread overview]
Message-ID: <CAPrcauMCb0epbES2-O7XaKTTVZySjABh1ApyDOZsSO74DnbEQw@mail.gmail.com> (raw)
In-Reply-To: <CAPrcauNxgWTW0T_G=hv8fVEo_xJy9xp8-bkj-G37RefvnhLONg@mail.gmail.com>

Sorry pressed the send button too soon. The NIC Card we are using is

Intel Corporation 82576 Virtual Function (rev 01)

Do we need to do now NIC/CPU low level debugging or is there some issue in
the sw that could cause the packet to be dropped below this log message.

PMD: eth_igb_xmit_pkts(): port_id=3 queue_id=0 pktlen=60 tx_first=14
tx_last=14

PMD: eth_igb_xmit_pkts(): port_id=3 queue_id=0 tx_tail=15 nb_tx=1

Thanks,
Sambath


On Sat, Nov 2, 2013 at 3:54 PM, Sambath Kumar Balasubramanian <
sambath.balasubramanian@gmail.com> wrote:

> Hi,
>
>   We are developing an App over DPDK and in one scenario with SR-IOV with
> one of the VFs mapped to a VM and DPDK running on the VM, we see that the
> packets are not coming on the wire but I get the following debug logs for
> every packet transmitted. We are getting the same format of packets on the
> wire in a different scenario so IMO the Virtual Function ports are set up
> properly. Any idea how this can be debugged further. The NIC card we are
> using is
>
>
>
> PMD: eth_igb_xmit_pkts(): port_id=3 queue_id=0 pktlen=60 tx_first=14
> tx_last=14
>
> PMD: eth_igb_xmit_pkts(): port_id=3 queue_id=0 tx_tail=15 nb_tx=1
>
> Regards,
> Sambath
>
>

  reply	other threads:[~2013-11-02 22:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-02 22:54 Sambath Kumar Balasubramanian
2013-11-02 22:56 ` Sambath Kumar Balasubramanian [this message]
2013-11-03 12:48   ` Prashant Upadhyaya
2013-11-03 13:18     ` Sambath Kumar Balasubramanian
2013-11-03 14:39       ` Sambath Kumar Balasubramanian

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=CAPrcauMCb0epbES2-O7XaKTTVZySjABh1ApyDOZsSO74DnbEQw@mail.gmail.com \
    --to=sambath.balasubramanian@gmail.com \
    --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).