DPDK usage discussions
 help / color / mirror / Atom feed
From: "VERDOUX, Sylvain" <s.verdoux@evs.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] How to debug I40E PMD RX/TX frees
Date: Mon, 17 Oct 2016 14:45:59 +0000	[thread overview]
Message-ID: <294AEAFC4B0A3E498038549EC65E9D1B018AB03E87@BELGSMBX01.EVS.TV> (raw)

Hello,

I am currently trying a small igmp sample test using dpdk I40E PMD (NIC is X710). The code is quite simple and uses 2 lcores to handle a recv loop on RX0 and a send loop on TX0. When the recv loop detects a query, it notifies the send loop to emit a report. I use at startup a fdir filter to move the mcast flow to another queue to not be polluted with this flow in my recv loop. For a while it works fine but after some time, the recv loop just stop retrieving queries, and I have difficulties debugging the problem. It seems like a mbuf free problem but even if I have activated I40E debug and mbuf debug in my dpdk config file then recompile it, I can't see any alarming message. For now I think that I free received mbufs properly and sent mbufs should be released by the tx_burst function, so I don't really understand the issue. So I'm asking if tools are available to debug deeply the problem ?

Thanks,
Best Regards

Sylvain

                 reply	other threads:[~2016-10-17 14:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=294AEAFC4B0A3E498038549EC65E9D1B018AB03E87@BELGSMBX01.EVS.TV \
    --to=s.verdoux@evs.com \
    --cc=users@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).