From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <simhelmut@gmail.com>
Received: from mail-we0-f173.google.com (mail-we0-f173.google.com
 [74.125.82.173]) by dpdk.org (Postfix) with ESMTP id 4DFAFB363
 for <dev@dpdk.org>; Wed, 16 Jul 2014 14:35:12 +0200 (CEST)
Received: by mail-we0-f173.google.com with SMTP id q58so854518wes.32
 for <dev@dpdk.org>; Wed, 16 Jul 2014 05:36:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=O93ifAzEVzp8q30qd77BczIk92/6b6/1/P87KCNZn4k=;
 b=FihpZkC0xMIvQmz4ZzqgtNFfIs2l7BuGLtcyMTHUF8f/tNdiMLE+F1IPKQKDWA/4pJ
 ULlRuIaRScMg9w0RJU7jdH5K2fvjYm/j0nhQhIJcGoIUMfarlynBgHQriCrHPM9VLPsy
 WlsJqQJFSEZt0zmAFT4bZoZ+0DQvZLGIAAO8bq3IkW+VkmtiSpaP61fpugkMshUJQKTO
 vK2Pcoq2gl9EnmhZTgibLDrYzq6AEB189qcDFUETfpBfvYVSdia4B+vCiKRe/mj4BnF7
 9MJ04eakoFHNZU3t9BvspNMlEMg5BkH/y6mzJT7cRX+hNwomYku/BH04MC36Q6FOkgR4
 njMg==
MIME-Version: 1.0
X-Received: by 10.194.85.78 with SMTP id f14mr36107867wjz.36.1405514163529;
 Wed, 16 Jul 2014 05:36:03 -0700 (PDT)
Received: by 10.194.139.167 with HTTP; Wed, 16 Jul 2014 05:36:03 -0700 (PDT)
In-Reply-To: <53C66DB2.4040605@6wind.com>
References: <CAF8yGaFKBYtSMY5so09Q0=Bs=_Y_toTG4w28ZttWVPQPspBtdA@mail.gmail.com>
 <CAF8yGaG1j+a8_NoaBKhvBRk7FiJUrG2eM-w2XKNr6tH69JdZdw@mail.gmail.com>
 <1912860.PvCxTjHaVZ@xps13> <53C66DB2.4040605@6wind.com>
Date: Wed, 16 Jul 2014 15:36:03 +0300
Message-ID: <CAF8yGaGkosEDmL3h4bQ9sm86+9=yBLcsyUtMBu+K7ps--J_Rxg@mail.gmail.com>
From: Helmut Sim <simhelmut@gmail.com>
To: Olivier MATZ <olivier.matz@6wind.com>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] phantom old packets received in new mbuf
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Jul 2014 12:35:12 -0000

I will try it though I hope the amount of logs won't affect the result.
while analyzing the wireshark captures I noted that the packet i supposed
to capture arrives in a short time after the one before.
for example, here is a time between the consecutive transmitted packets:
0.000050000 PKT 12201
0.000050000 PKT 12202
0.000050000 PKT 12203
0.000050000 PKT 12204
0.000050000 PKT 12205
0.000050000 PKT 12206
0.000020000 PKT 12207 ==> though this one was received at the app as "PKT
12202"
0.000050000 PKT 12208

note that the problematic case was transmitted in a very short time after
its previous one. this is also the case in other problematic cases.

is there any way to configure ethernet IFG (Interf Frame Gap)?

Thanks,


On Wed, Jul 16, 2014 at 3:18 PM, Olivier MATZ <olivier.matz@6wind.com>
wrote:

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