From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <huawei.xie@intel.com>
Received: from mga11.intel.com (mga11.intel.com [192.55.52.93])
 by dpdk.org (Postfix) with ESMTP id 731F8370
 for <dev@dpdk.org>; Wed, 13 Jan 2016 13:48:57 +0100 (CET)
Received: from orsmga001.jf.intel.com ([10.7.209.18])
 by fmsmga102.fm.intel.com with ESMTP; 13 Jan 2016 04:48:56 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.22,289,1449561600"; d="scan'208";a="859642417"
Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201])
 by orsmga001.jf.intel.com with ESMTP; 13 Jan 2016 04:48:56 -0800
Received: from fmsmsx111.amr.corp.intel.com (10.18.116.5) by
 FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS)
 id 14.3.248.2; Wed, 13 Jan 2016 04:48:55 -0800
Received: from shsmsx104.ccr.corp.intel.com (10.239.110.15) by
 fmsmsx111.amr.corp.intel.com (10.18.116.5) with Microsoft SMTP Server (TLS)
 id 14.3.248.2; Wed, 13 Jan 2016 04:48:55 -0800
Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.215]) by
 SHSMSX104.ccr.corp.intel.com ([169.254.5.117]) with mapi id 14.03.0248.002;
 Wed, 13 Jan 2016 20:48:54 +0800
From: "Xie, Huawei" <huawei.xie@intel.com>
To: Pavel Fedin <p.fedin@samsung.com>, "dev@dpdk.org" <dev@dpdk.org>
Thread-Topic: [dpdk-dev] [RESEND PATCH] vhost_user: Make sure that memory
 map is set before attempting address translation
Thread-Index: AdFN5C2FcQQ+0NIpQtu+e7/JrHFEcQ==
Date: Wed, 13 Jan 2016 12:48:53 +0000
Message-ID: <C37D651A908B024F974696C65296B57B4C589C81@SHSMSX101.ccr.corp.intel.com>
References: <005a01d14dd4$a02c5340$e084f9c0$@samsung.com>
 <C37D651A908B024F974696C65296B57B4C5827EE@SHSMSX101.ccr.corp.intel.com>
 <006a01d14de6$69c68610$3d539230$@samsung.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.16.213.225]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dpdk-dev] [RESEND PATCH] vhost_user: Make sure that memory map
 is set before attempting address translation
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, 13 Jan 2016 12:48:57 -0000

On 1/13/2016 5:40 PM, Pavel Fedin wrote:=0A=
>  Hello!=0A=
>=0A=
>> Do you have examples for the malfunctioning clients? If so, could you=0A=
>> list them in the commit message?=0A=
>  The only malfunctioning client was DPDK itself, with virtio for containe=
r RFC applied. The client-side problem has been fixed=0A=
> afterwards by http://dpdk.org/ml/archives/dev/2016-January/031169.html. S=
ee the RFC discussion thread.=0A=
=0A=
If this is the case, i am wondering whether we should include=0A=
"malfunctioning clients" in commit message. It triggers me to think if=0A=
there are existing buggy implementations.=0A=
=0A=
Anyway, check is OK.=0A=
=0A=
> Kind regards,=0A=
> Pavel Fedin=0A=
> Senior Engineer=0A=
> Samsung Electronics Research center Russia=0A=
>=0A=
>=0A=
>=0A=
=0A=