From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <haifeng.lin@huawei.com> Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by dpdk.org (Postfix) with ESMTP id E5D02DE0 for <dev@dpdk.org>; Fri, 12 Dec 2014 03:26:07 +0100 (CET) Received: from 172.24.2.119 (EHLO szxeml448-hub.china.huawei.com) ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CFY40857; Fri, 12 Dec 2014 10:26:05 +0800 (CST) Received: from [127.0.0.1] (10.177.19.115) by szxeml448-hub.china.huawei.com (10.82.67.191) with Microsoft SMTP Server id 14.3.158.1; Fri, 12 Dec 2014 10:26:00 +0800 Message-ID: <548A5237.9030805@huawei.com> Date: Fri, 12 Dec 2014 10:25:59 +0800 From: Linhaifeng <haifeng.lin@huawei.com> User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.1.0 MIME-Version: 1.0 To: "Xie, Huawei" <huawei.xie@intel.com>, "dev@dpdk.org" <dev@dpdk.org> References: <1418247477-13920-1-git-send-email-huawei.xie@intel.com> <1418247477-13920-9-git-send-email-huawei.xie@intel.com> <548933D8.5000908@huawei.com> <C37D651A908B024F974696C65296B57B0F31FBD1@SHSMSX101.ccr.corp.intel.com> In-Reply-To: <C37D651A908B024F974696C65296B57B0F31FBD1@SHSMSX101.ccr.corp.intel.com> Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.177.19.115] X-CFilter-Loop: Reflected Cc: "haifeng.lin@intel.com" <haifeng.lin@intel.com> Subject: Re: [dpdk-dev] [PATCH RFC v2 08/12] lib/librte_vhost: vhost-user support 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: Fri, 12 Dec 2014 02:26:09 -0000 On 2014/12/12 1:13, Xie, Huawei wrote: >> >> Only support one vhost-user port ? > > Do you mean vhost server by "port"? > If that is the case, yes, now only one vhost server is supported for multiple virtio devices. > As stated in the cover letter, we have requirement and plan for multiple server support, > though I am not sure if it is absolutely necessary. > I think if you also want to suport client mode (qemu as server) is necessary to implement multiple server. >> >> Can you mmap the region if gpa is 0? When i run VM with two numa node (qemu >> will create two hugepage file) found that always failed to mmap with the region >> which gpa is 0. > > Current implementation doesn't assume there is only one huge page file to back the guest memory. > It maps every region using the fd of that region. > Could you please paste your guest VM command line here? > >> >> BTW can we ensure the memory regions cover with all the memory of hugepage >> for VM? > > I think so, because virtio devices could use any normal guest memory, but we needn't ensure that. > We only need to map the region passed to us from qemu vhost, which should be enough to translate > the GPA in vring from virtio in guest, otherwise it is the bug of qemu vhost. > > -- Regards, Haifeng