From mboxrd@z Thu Jan  1 00:00:00 1970
From: Tetsuya Mukawa <mukawa@igel.co.jp>
Subject: Re: [RFC PATCH 5/5] virtio: Extend virtio-net PMD to
 support container environment
Date: Thu, 28 Jan 2016 11:33:27 +0900
Message-ID: <56A97DF7.702@igel.co.jp>
References: <1453108389-21006-2-git-send-email-mukawa@igel.co.jp>
 <1453374478-30996-6-git-send-email-mukawa@igel.co.jp>
 <C37D651A908B024F974696C65296B57B4C5A9001@SHSMSX101.ccr.corp.intel.com>
 <56A2065A.9020207@igel.co.jp>
 <C37D651A908B024F974696C65296B57B4C5ACAC5@SHSMSX101.ccr.corp.intel.com>
 <56A6E0D8.9010005@igel.co.jp>
 <C37D651A908B024F974696C65296B57B4C5B144A@SHSMSX101.ccr.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
To: "Xie, Huawei" <huawei.xie@intel.com>, "dev@dpdk.org" <dev@dpdk.org>,
 "yuanhan.liu@linux.intel.com" <yuanhan.liu@linux.intel.com>,
 "Tan, Jianfeng" <jianfeng.tan@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-pf0-f182.google.com (mail-pf0-f182.google.com
 [209.85.192.182]) by dpdk.org (Postfix) with ESMTP id 497AEC2DC
 for <dev@dpdk.org>; Thu, 28 Jan 2016 03:33:32 +0100 (CET)
Received: by mail-pf0-f182.google.com with SMTP id 65so14991877pfd.2
 for <dev@dpdk.org>; Wed, 27 Jan 2016 18:33:32 -0800 (PST)
In-Reply-To: <C37D651A908B024F974696C65296B57B4C5B144A@SHSMSX101.ccr.corp.intel.com>
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>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

On 2016/01/27 18:39, Xie, Huawei wrote:
> On 1/26/2016 10:58 AM, Tetsuya Mukawa wrote:
>> On 2016/01/25 19:15, Xie, Huawei wrote:
>>
>> BTW, my container implementation needed a QEMU patch in the case of
>> vhost-user.
>> But the patch has been merged in upstream QEMU, so we don't have this
>> limitation any more.
> Great, better put the QEMU dependency information in the commit message

Thanks for all your comments and carefully reviewing.

So far, I am not sure what is next QEMU version.
But I will add it after QEMU releases new one.

Tetsuya