From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: "André Przywara" <osp@andrep.de>, kvm@vger.kernel.org
Subject: Re: [PATCH 0/3] v2: KVM-userspace: add NUMA support for guests
Date: Tue, 09 Dec 2008 08:55:17 -0600 [thread overview]
Message-ID: <493E86D5.5040602@codemonkey.ws> (raw)
In-Reply-To: <493E7FB5.80606@redhat.com>
Avi Kivity wrote:
> André Przywara wrote:
>>>> But I wouldn't load the admin with the burden of pinning, but let
>>>> this be done by QEMU/KVM. Maybe one could introduce a way to tell
>>>> QEMU/KVM to not pin the threads.
>>> This is where things start to get ugly...
>> Why? qemu-system-x86_64 -numa 2,pin:none and then use whatever method
>> you prefer (taskset, monitor) to pin the VCPUs (or left them unpinned).
>
> I agree that for e.g. -numa 2, no host binding should occur. Pinning
> memory or cpus to nodes should only occur if the user explicitly
> requested it. Otherwise we run the risk of breaking load balancing.
>
> If the user chooses to pin, the responsibility is on them. If not, we
> should allow the host to do its thing.
Agreed.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2008-12-09 14:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-05 13:29 [PATCH 0/3] v2: KVM-userspace: add NUMA support for guests Andre Przywara
2008-12-05 14:28 ` Anthony Liguori
2008-12-05 15:22 ` Andre Przywara
2008-12-05 15:41 ` Anthony Liguori
2008-12-08 21:46 ` André Przywara
2008-12-08 22:01 ` Anthony Liguori
2008-12-09 14:24 ` Avi Kivity
2008-12-09 14:55 ` Anthony Liguori [this message]
2008-12-05 15:27 ` Avi Kivity
2008-12-05 15:34 ` Anthony Liguori
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=493E86D5.5040602@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=osp@andrep.de \
/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;
as well as URLs for NNTP newsgroup(s).