From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas.monjalon@6wind.com>
Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com
 [209.85.212.180]) by dpdk.org (Postfix) with ESMTP id A210DC5EE
 for <dev@dpdk.org>; Mon, 22 Jun 2015 18:34:41 +0200 (CEST)
Received: by wicnd19 with SMTP id nd19so82058926wic.1
 for <dev@dpdk.org>; Mon, 22 Jun 2015 09:34:41 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:from:to:cc:subject:date:message-id:organization
 :user-agent:in-reply-to:references:mime-version
 :content-transfer-encoding:content-type;
 bh=BlpTUs0eVV4eX1bbjV3YZJkcHkeuaVknCl9/yfClzq4=;
 b=F3bRVAQHN29Hse5F0fmRGQtfDKObuFTgJVC1rH7NBMeUNhxyACqcm79/Ui6FSSQ8XP
 Sk5Wr7VPd8jja3e5HP2Bl79Xb+gvHU33borl0mmLwNj9Dc9ojIZ2fIXP1c3lYztR1yCU
 tGpYmVhYGTZqPX++hBmrxyQPhShpGXpDG20aI3cxObTAmZpzUCM642AHzYeXK+Ql/sKv
 ju85QJ97ZgAqic8Jn7tkXZDCUzyE8OwkfjILy6ECgUe78Szuh0w+eAqSQVUhB3715iMA
 4f9nlU6XojVqogEe4v96T+BURj/3Tb5rJJpKlbngkU6aIpK9k9EFE/ZDCX4HrdjASJyn
 m+tg==
X-Gm-Message-State: ALoCoQkUQu+k8x9X5CyD+NZ6y71wIhzedczZrOSQyeAIxzknveqOohS7Extrm25GhkpjzTvzofmI
X-Received: by 10.194.82.167 with SMTP id j7mr53635417wjy.123.1434990881358;
 Mon, 22 Jun 2015 09:34:41 -0700 (PDT)
Received: from xps13.localnet (136-92-190-109.dsl.ovh.fr. [109.190.92.136])
 by mx.google.com with ESMTPSA id u7sm18049424wif.3.2015.06.22.09.34.39
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Mon, 22 Jun 2015 09:34:40 -0700 (PDT)
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Ouyang, Changchun" <changchun.ouyang@intel.com>, Wei li <liw@dtdream.com>
Date: Mon, 22 Jun 2015 18:33:38 +0200
Message-ID: <5707625.FvquhSeuHS@xps13>
Organization: 6WIND
User-Agent: KMail/4.14.8 (Linux/4.0.4-2-ARCH; KDE/4.14.8; x86_64; ; )
In-Reply-To: <F52918179C57134FAEC9EA62FA2F962511B74CEC@shsmsx102.ccr.corp.intel.com>
References: <72a55103-9c65-4f2e-9448-919622dbac81@liw0310-PC.local>
 <F52918179C57134FAEC9EA62FA2F962511B74CEC@shsmsx102.ccr.corp.intel.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] lib_vhost:reset secure_len when
	rte_atomic16_cmpset failed
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, 22 Jun 2015 16:34:41 -0000

2015-06-01 06:14, Ouyang, Changchun:
> From: Wei li, June 1, 2015 2:12 PM:
> > when rte_atomic16_cmpset return 0 in first loop, secure_len  should be
> > reset to 0 in second loop, otherwise (pkt_len > secure_len) always  be false,
> > the num of desc maybe not enough
> > 
> > Signed-off-by: Wei li <liw@dtdream.com>
> 
> Acked-by: Changchun Ouyang<changchun.ouyang@intel.com>

Is it already fixed by this commit?
	http://dpdk.org/browse/dpdk/commit/?id=2927c37ca4e04067