From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mukawa@igel.co.jp>
Received: from mail-pb0-f46.google.com (mail-pb0-f46.google.com
 [209.85.160.46]) by dpdk.org (Postfix) with ESMTP id 0A27A156
 for <dev@dpdk.org>; Mon, 14 Apr 2014 09:20:50 +0200 (CEST)
Received: by mail-pb0-f46.google.com with SMTP id rq2so7853210pbb.5
 for <dev@dpdk.org>; Mon, 14 Apr 2014 00:20:50 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to
 :cc:subject:references:in-reply-to:content-type
 :content-transfer-encoding;
 bh=ME7y9hwvj4xboECKQBbrqPHZ8EqIPVzNeqd4W0eLGbU=;
 b=FI2/qn8ifsyRWpTeZFqm/IvtboJCrsZWApKCmiT6kJTgCvnc0+FKhvV9lHdo1gTwPC
 hoVqnwbDmc2/pa7f5g06JwdJF2JqiY/lnCTDJWt3ozlpzjXINweTzNdnG1hkkvxxMAtG
 qA/SrBJOzz4q4D7UFb6aOAOhcMdEFkd4vFcmlx59gXdSY3EpkUT9U6Q9ClTpmXfdhyGh
 hnNxjMdT2qRvXR5/kX50kXZV+Rh7N4onEzfOz7+oZ5Hg4c6uEbmNh0sVxanCeSHfxSr8
 VK1bHe0tJweRpL4QKRBDhw+pXq+9lvNp+nS7fobyDnD6kd13iWpuYaZnormkh78Tsvh8
 Lkrw==
X-Gm-Message-State: ALoCoQmw2YS506KACTJFJdeBiiBtpuuq0jQ5UOEMjnk/ZkACXR5QkN/nPINvDfyvKD9ysCAJD6CM
X-Received: by 10.66.122.1 with SMTP id lo1mr1984844pab.118.1397460050434;
 Mon, 14 Apr 2014 00:20:50 -0700 (PDT)
Received: from [10.16.129.101] (napt.igel.co.jp. [219.106.231.132])
 by mx.google.com with ESMTPSA id de5sm31870372pbc.66.2014.04.14.00.20.49
 for <multiple recipients>
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Mon, 14 Apr 2014 00:20:49 -0700 (PDT)
Message-ID: <534B8C52.8070003@igel.co.jp>
Date: Mon, 14 Apr 2014 16:20:50 +0900
From: "Tetsuya.Mukawa" <mukawa@igel.co.jp>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Meir Tseitlin <mirots@gmail.com>, dev@dpdk.org
References: <CA+Typ9mstsAQEHaYCAa39gKY9EHObkzeTXcav_5s9Gr5xNY7xg@mail.gmail.com>
In-Reply-To: <CA+Typ9mstsAQEHaYCAa39gKY9EHObkzeTXcav_5s9Gr5xNY7xg@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dpdk-dev] Weird behavior of DPDK - ongoing problem
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: Mon, 14 Apr 2014 07:20:51 -0000

Hi Meir,

(2014/04/13 19:21), Meir Tseitlin wrote:
> The problem is that in 30% of the cases data packet enters the path of
> control packet instead of expected answer. Which probably means that after
> my packet type check, the mbuf is overwritten before handled properly.
If you are using DPDK-1.5, it's nice to update to DPDK-1.6, because pcap
pmd of DPDK-1.5 has buffer overflow while receiving  data from a target
device/file. And the issue was solved with DPDK-1.6 (in both intel
original code and dpdk.org code).

Also if multiple processes/threads run on a same cpu, probably, it could
cause a problem like you're facing.

Regards,
Tetsuya