From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id D88315A8B for ; Thu, 4 Jun 2015 01:38:31 +0200 (CEST) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga101.fm.intel.com with ESMTP; 03 Jun 2015 16:38:28 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.13,549,1427785200"; d="scan'208";a="581686094" Received: from irsmsx108.ger.corp.intel.com ([163.33.3.3]) by orsmga003.jf.intel.com with ESMTP; 03 Jun 2015 16:38:28 -0700 Received: from irsmsx104.ger.corp.intel.com ([169.254.5.27]) by IRSMSX108.ger.corp.intel.com ([169.254.11.59]) with mapi id 14.03.0224.002; Thu, 4 Jun 2015 00:38:27 +0100 From: "Long, Thomas" To: "Xie, Huawei" , "dev@dpdk.org" Thread-Topic: [dpdk-dev] [PATCH RFC 0/2] vhost: numa aware allocation of virtio_net device and vhost virt queue Thread-Index: AQHQmOqxLVNRZkZe3E6S3+MmnYevD52bebQA Date: Wed, 3 Jun 2015 23:38:27 +0000 Message-ID: References: <1432778661-25428-1-git-send-email-huawei.xie@intel.com> In-Reply-To: <1432778661-25428-1-git-send-email-huawei.xie@intel.com> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH RFC 0/2] vhost: numa aware allocation of virtio_net device and vhost virt queue 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: Wed, 03 Jun 2015 23:38:32 -0000 Acked-by: Tommy Long -----Original Message----- From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Huawei Xie Sent: Thursday, May 28, 2015 3:04 AM To: dev@dpdk.org Subject: [dpdk-dev] [PATCH RFC 0/2] vhost: numa aware allocation of virtio_= net device and vhost virt queue The virtio_net device and vhost virt queue should be allocated on the same = numa node as vring descriptors. When we firstly allocate the virtio_net device and vhost virt queue, we don= 't know the numa node of vring descriptors. When we receive the VHOST_SET_VRING_ADDR message, we get the numa node of v= ring descriptors, so we will try to reallocate virtio_net and vhost virt qu= eue to the same numa node. Huawei Xie (2): use rte_malloc/free for virtio_net and virt_queue memory data allocation/= free When we get the address of vring descriptor table, will try to reallocate= virtio_net device and virtqueue to the same numa node. config/common_linuxapp | 1 + lib/librte_vhost/Makefile | 4 ++ lib/librte_vhost/virtio-net.c | 112 ++++++++++++++++++++++++++++++++++++++= ---- mk/rte.app.mk | 3 ++ 4 files changed, 111 insertions(+), 9 deletions(-) --=20 1.8.1.4