From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id DEB89282 for ; Mon, 26 Jan 2015 08:24:56 +0100 (CET) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga102.jf.intel.com with ESMTP; 25 Jan 2015 23:21:45 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.09,467,1418112000"; d="scan'208";a="675861849" Received: from pgsmsx103.gar.corp.intel.com ([10.221.44.82]) by orsmga002.jf.intel.com with ESMTP; 25 Jan 2015 23:24:54 -0800 Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by PGSMSX103.gar.corp.intel.com (10.221.44.82) with Microsoft SMTP Server (TLS) id 14.3.195.1; Mon, 26 Jan 2015 15:24:37 +0800 Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.64]) by SHSMSX151.ccr.corp.intel.com ([169.254.3.92]) with mapi id 14.03.0195.001; Mon, 26 Jan 2015 15:24:36 +0800 From: "Xie, Huawei" To: Linhaifeng , "dev@dpdk.org" Thread-Topic: [dpdk-dev] [PATCH RFC v2 00/12] lib/librte_vhost: vhost-user support Thread-Index: AQHQNuT7JDx4kuOaJEe3zdmcGyMxzZzSAJzg Date: Mon, 26 Jan 2015 07:24:35 +0000 Message-ID: References: <1418247477-13920-1-git-send-email-huawei.xie@intel.com> <54C20361.1090105@huawei.com> In-Reply-To: <54C20361.1090105@huawei.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH RFC v2 00/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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jan 2015 07:24:57 -0000 > -----Original Message----- > From: Linhaifeng [mailto:haifeng.lin@huawei.com] > Sent: Friday, January 23, 2015 4:17 PM > To: Xie, Huawei; dev@dpdk.org > Cc: haifeng.lin@intel.com > Subject: Re: [dpdk-dev] [PATCH RFC v2 00/12] lib/librte_vhost: vhost-user > support >=20 > Hi, Xie >=20 > could you test vhost-user with follow numa node xml: > 2097152 > > > > > > >=20 >=20 > I cann't receive data from VM with above xml. >=20 1.=20 I guess you want to configure numa memory for guest, and the xml should be: , right? Otherwise you are specifying the same memdev id, which cause qemu fail to = boot. 2. >>From the following output, qemu uses two hugepage files to map guest memory= , \ while we receive two fds "pointing to the same hugepage file". This should be a qemu bug. I recall there is bug related to memory mapping with multiple node, right? We will recommend customers not to configure multiple memory node in guest= until the bug is fixed in qemu. # ls /proc/`pgrep qemu`/fd -l | grep huge lrwx------. 1 root root 64 Jan 25 23:09 7 -> /mnt/huge/qemu_back_mem._objec= ts_mem0.UfvViC (deleted) lrwx------. 1 root root 64 Jan 25 23:09 8 -> /mnt/huge/qemu_back_mem._objec= ts_mem1.kuX5tu (deleted) # cat /proc/`pgrep qemu`/maps | grep huge 2aaac0000000-2aab00000000 rw-s 00000000 00:20 2674754 /m= nt/huge/qemu_back_mem._objects_mem0.UfvViC (deleted) 2aab00000000-2aab40000000 rw-s 00000000 00:20 2674755 /m= nt/huge/qemu_back_mem._objects_mem1.kuX5tu (deleted) (gdb) p /x *memory.regions@memory.nregions $21 =3D {{guest_phys_addr =3D 0xc0000, memory_size =3D 0x7ff40000, userspac= e_addr =3D 0x2aaac00c0000, mmap_offset =3D 0xc0000}, {guest_phys_addr =3D 0x0, memory_size =3D 0xa= 0000, userspace_addr =3D 0x2aaac0000000, mmap_offset =3D 0x0}} #ls -l /proc/`pgrep vhost`/fd | grep qemu_back lrwx------. 1 root root 64 Jan 25 23:18 22 -> /mnt/huge/qemu_back_mem._obje= cts_mem0.UfvViC (deleted) lrwx------. 1 root root 64 Jan 25 23:18 24 -> /mnt/huge/qemu_back_mem._obje= cts_mem0.UfvViC (deleted)