From: Olivier MATZ <olivier.matz@6wind.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
Helmut Sim <simhelmut@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] phantom old packets received in new mbuf
Date: Wed, 16 Jul 2014 14:18:58 +0200 [thread overview]
Message-ID: <53C66DB2.4040605@6wind.com> (raw)
In-Reply-To: <1912860.PvCxTjHaVZ@xps13>
Hello Helmut,
2014-07-16 13:56, Helmut Sim:
>> then i see that from time to time i get a packet that was already received
>> earlier instead of receiving the expected packet.
>> the output is:
>> PKT 12201
>> PKT 12202
>> PKT 12203
>> PKT 12204
>> PKT 12205
>> PKT 12206
>> PKT 12202
>> PKT 12208
>>
>> total received pkts is identical to the total delivered pkts, but part of
>> the pkts are being received twice...
Enabling CONFIG_RTE_LIBRTE_MEMPOOL_DEBUG and
CONFIG_RTE_LIBRTE_MBUF_DEBUG could help you to track
double free or corruptions.
Regards,
Olivier
next prev parent reply other threads:[~2014-07-16 12:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-06 15:19 Helmut Sim
2014-07-16 10:56 ` Helmut Sim
2014-07-16 12:04 ` Thomas Monjalon
2014-07-16 12:18 ` Olivier MATZ [this message]
2014-07-16 12:36 ` Helmut Sim
2014-07-16 13:22 ` Helmut Sim
2014-07-17 8:39 ` Helmut Sim
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=53C66DB2.4040605@6wind.com \
--to=olivier.matz@6wind.com \
--cc=dev@dpdk.org \
--cc=simhelmut@gmail.com \
--cc=thomas.monjalon@6wind.com \
/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).