qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: gaowanlong@cn.fujitsu.com
Cc: andre.przywara@amd.com, Anthony Liguori <aliguori@us.ibm.com>,
	Eduardo Habkost <ehabkost@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] Add monitor command mem-nodes
Date: Sat, 15 Jun 2013 13:23:11 -0400	[thread overview]
Message-ID: <51BCA2FF.7090302@redhat.com> (raw)
In-Reply-To: <51BA6EEA.20901@cn.fujitsu.com>

Il 13/06/2013 21:16, Wanlong Gao ha scritto:
> On 06/14/2013 09:05 AM, Anthony Liguori wrote:
>> Paolo Bonzini <pbonzini@redhat.com> writes:
>>
>>> Il 13/06/2013 08:50, Eduardo Habkost ha scritto:
>>>> I believe an interface based on guest physical memory addresses is more
>>>> flexible (and even simpler!) than one that only allows binding of whole
>>>> virtual NUMA nodes.
>>>
>>> And "-numa node" is already one, what about just adding "mem-path=/foo"
>>> or "host_node=NN" suboptions?  Then "-mem-path /foo" would be a shortcut
>>> for "-numa node,mem-path=/foo".
>>>
>>> I even had patches to convert -numa to QemuOpts, I can dig them out if
>>> your interested.
>>
>> Ack.  This is a very reasonable thing to add.
> 
> How about making "-numa node,membind=0" like options, and also provide a
> QMP interface "numa_set guest_node_id mempolicy". So that we can set
> the mempolicy not only for file backed memory but also for anon mapped
> guest numa node. This is full numa support in QEMU as you said. I'm making
> the patches now.

Yup, that's exactly what I called "host_node".  membind also makes
sense, but make it mem-bind or mem-host-node for consistency with mem-path.

Paolo

  reply	other threads:[~2013-06-15 17:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-05  3:58 [Qemu-devel] [PATCH 1/2] Add Linux libnuma detection Wanlong Gao
2013-06-05  3:58 ` [Qemu-devel] [PATCH 2/2] Add monitor command mem-nodes Wanlong Gao
2013-06-05 12:39   ` Eric Blake
2013-06-05 12:57   ` Anthony Liguori
2013-06-05 15:54     ` Eduardo Habkost
2013-06-06  9:30       ` Wanlong Gao
2013-06-06 16:15         ` Eduardo Habkost
2013-06-14  1:04       ` Anthony Liguori
2013-06-14 13:56         ` Eduardo Habkost
2013-06-05 13:46   ` Eduardo Habkost
2013-06-11  7:22     ` Wanlong Gao
2013-06-11 13:40       ` Eduardo Habkost
2013-06-13  1:40         ` Wanlong Gao
2013-06-13 12:50           ` Eduardo Habkost
2013-06-13 22:32             ` Paolo Bonzini
2013-06-14  1:05               ` Anthony Liguori
2013-06-14  1:16                 ` Wanlong Gao
2013-06-15 17:23                   ` Paolo Bonzini [this message]
2013-06-05 10:02 ` [Qemu-devel] [PATCH 1/2] Add Linux libnuma detection Andreas Färber

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=51BCA2FF.7090302@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=andre.przywara@amd.com \
    --cc=ehabkost@redhat.com \
    --cc=gaowanlong@cn.fujitsu.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).