public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Andre Przywara <andre.przywara@amd.com>, kvm@vger.kernel.org
Subject: Re: [PATCH 0/3] KVM-userspace: add NUMA support for guests
Date: Mon, 01 Dec 2008 17:35:16 +0200	[thread overview]
Message-ID: <49340434.80300@redhat.com> (raw)
In-Reply-To: <4934002C.7070507@codemonkey.ws>

Anthony Liguori wrote:
> Andre Przywara wrote:
>> Hi,
>>
>> this patch series introduces multiple NUMA nodes support within KVM 
>> guests.
>> This will improve the performance of guests which are bigger than one 
>> node (number of VCPUs and/or amount of memory) and also allows better 
>> balancing by taking better usage of each node's memory.
>> It also improves the one node case by pinning a guest to this node and
>> avoiding access of remote memory from one VCPU.
>
> Could you please post this to qemu-devel?  There's really nothing KVM 
> specific here.
>

It's almost useless to qemu until it can run vcpus on host threads.  I 
agree it should be posted there though.

>
> I think the dependency on libnuma is a bad idea.  It's mixing a 
> mechanism (emulating NUMA layout) with a policy (how to do memory/VCPU 
> placement).
>
> If you split the NUMA emulation bits into a separate patch series, 
> that has no dependency on the host NUMA topology, I think we look at 
> the existing mechanisms we have to see if they're sufficient to do 
> static placement on NUMA boundaries.  vcpu pinning is easy enough, I 
> think the only place we're lacking is memory layout.  Note, that's 
> totally independent of the guest's NUMA characteristics though.  You 
> may still want half of memory to be pinned between two nodes even if 
> the guest has no SRAT tables.

You can do that easily with numactl.  Fine grained control of host numa 
layout and guest numa emulation are only useful together (one could 
argue that guest numa emulation is useful by itself, for debugging the 
guest OS numa algorithms).

-- 
error compiling committee.c: too many arguments to function


      reply	other threads:[~2008-12-01 15:35 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-27 22:23 [PATCH 0/3] KVM-userspace: add NUMA support for guests Andre Przywara
2008-11-28  8:14 ` Andi Kleen
2008-11-29 18:43   ` Avi Kivity
2008-11-29 20:10     ` Andi Kleen
2008-11-29 20:35       ` Avi Kivity
2008-11-30 15:41         ` Andi Kleen
2008-11-30 15:38           ` Avi Kivity
2008-11-30 16:05             ` Andi Kleen
2008-11-30 16:38               ` Avi Kivity
2008-11-30 17:04                 ` Andi Kleen
2008-11-30 17:11                   ` Avi Kivity
2008-11-30 17:42                     ` Andi Kleen
2008-11-30 18:07                       ` Avi Kivity
2008-11-30 18:55                         ` Andi Kleen
2008-11-30 19:11                           ` Skywing
2008-11-30 20:08                             ` Avi Kivity
2008-11-30 20:07                           ` Avi Kivity
2008-11-30 21:41                             ` Andi Kleen
2008-11-30 21:50                               ` Avi Kivity
2008-11-30 22:08                                 ` Skywing
2008-11-28 10:40 ` Daniel P. Berrange
2008-11-29 18:29 ` Avi Kivity
2008-12-01 14:15   ` Andre Przywara
2008-12-01 14:29     ` Avi Kivity
2008-12-01 15:27       ` Anthony Liguori
2008-12-01 15:34         ` Anthony Liguori
2008-12-01 15:37         ` Avi Kivity
2008-12-01 15:49           ` Anthony Liguori
2008-12-01 14:44     ` Daniel P. Berrange
2008-12-01 14:53       ` Avi Kivity
2008-12-01 15:18 ` Anthony Liguori
2008-12-01 15:35   ` Avi Kivity [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49340434.80300@redhat.com \
    --to=avi@redhat.com \
    --cc=andre.przywara@amd.com \
    --cc=anthony@codemonkey.ws \
    --cc=kvm@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox