From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 0/3][RFC] NUMA: add host side pinning Date: Tue, 29 Jun 2010 12:48:36 +0300 Message-ID: <4C29C174.6030501@redhat.com> References: <1277327377-29629-1-git-send-email-andre.przywara@amd.com> <4C2288DD.3020207@codemonkey.ws> <865764AB-4E51-4ED4-8832-AED6A237A9D3@suse.de> <4C233A6D.7030805@amd.com> <4C233DAB.60106@redhat.com> <4C28CB33.8030101@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Andre Przywara , Alexander Graf , "kvm@vger.kernel.org" To: Anthony Liguori Return-path: Received: from mx1.redhat.com ([209.132.183.28]:28728 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754660Ab0F2Jsm (ORCPT ); Tue, 29 Jun 2010 05:48:42 -0400 In-Reply-To: <4C28CB33.8030101@codemonkey.ws> Sender: kvm-owner@vger.kernel.org List-ID: On 06/28/2010 07:17 PM, Anthony Liguori wrote: > On 06/24/2010 06:12 AM, Avi Kivity wrote: >> On 06/24/2010 01:58 PM, Andre Przywara wrote: >>>> So who would create the /dev/shm/nodeXX files? >>> >>> Currently it is QEMU. It creates a somewhat unique filename, opens >>> and unlinks it. The difference would be to name the file after the >>> option and to not unlink it. >>> >>> > I can imagine starting numactl before qemu, even though that's >>> > cumbersome. I don't think it's feasible to start numactl after >>> > qemu is running. That'd involve way too much magic that I'd prefer >>> > qemu to call numactl itself. >>> Using the current code the files would not exist before QEMU >>> allocated RAM, and after that it could already touch pages before >>> numactl set the policy. >> >> Non-anonymous memory doesn't work well with ksm and transparent >> hugepages. Is it possible to use anonymous memory rather than file >> backed? > > You aren't going to be doing NUMA pinning and KSM AFAICT. What about transparent hugepages? Conceptually, all of this belongs in the scheduler, so whatever we do ends up a poorly integrated hack. -- error compiling committee.c: too many arguments to function