From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] vhost: Fix retrieval of numa information in PMD Date: Wed, 06 Apr 2016 18:45:52 +0200 Message-ID: <1819068.kZbQtThe3g@xps13> References: <1459872587-11655-1-git-send-email-ciara.loftus@intel.com> <20160406050345.GS3080@yliu-dev.sh.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, Yuanhan Liu , mukawa@igel.co.jp To: Ciara Loftus Return-path: Received: from mail-wm0-f49.google.com (mail-wm0-f49.google.com [74.125.82.49]) by dpdk.org (Postfix) with ESMTP id 4AF622C69 for ; Wed, 6 Apr 2016 18:47:31 +0200 (CEST) Received: by mail-wm0-f49.google.com with SMTP id f198so81806460wme.0 for ; Wed, 06 Apr 2016 09:47:31 -0700 (PDT) In-Reply-To: <20160406050345.GS3080@yliu-dev.sh.intel.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2016-04-06 13:03, Yuanhan Liu: > On Tue, Apr 05, 2016 at 05:09:47PM +0100, Ciara Loftus wrote: > > After some testing, it was found that retrieving numa information > > about a vhost device via a call to get_mempolicy is more > > accurate when performed during the new_device callback versus > > the vring_state_changed callback, in particular upon initial boot > > of the VM. Performing this check during new_device is also > > potentially more efficient as this callback is only triggered once > > during device initialisation, compared with vring_state_changed > > which may be called multiple times depending on the number of > > queues assigned to the device. > > > > Reorganise the code to perform this check and assign the correct > > socket_id to the device during the new_device callback. > > > > Signed-off-by: Ciara Loftus > > Acked-by: Yuanhan Liu Fixes: ee584e9710b9 ("vhost: add driver on top of the library") Applied, thanks