qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: aliguori@us.ibm.com, ehabkost@redhat.com, lersek@redhat.com,
	qemu-devel@nongnu.org, lcapitulino@redhat.com, bsd@redhat.com,
	hutao@cn.fujitsu.com, y-goto@jp.fujitsu.com,
	peter.huangpeng@huawei.com, afaerber@suse.de,
	Wanlong Gao <gaowanlong@cn.fujitsu.com>
Subject: Re: [Qemu-devel] [PATCH V8 00/11] Add support for binding guest numa nodes to host numa nodes
Date: Wed, 21 Aug 2013 17:08:26 +0800	[thread overview]
Message-ID: <5214838A.3090501@cn.fujitsu.com> (raw)
In-Reply-To: <521481B9.9070604@redhat.com>

On 08/21/2013 05:00 PM, Paolo Bonzini wrote:
> Il 21/08/2013 03:22, Wanlong Gao ha scritto:
>> On 08/20/2013 09:43 PM, Paolo Bonzini wrote:
>>> Il 20/08/2013 03:07, Wanlong Gao ha scritto:
>>>>  -numa node,nodeid=0,cpus=0, \
>>>>  -numa mem,size=1024M,policy=membind,host-nodes=0-1 \
>>>>  -numa node,nodeid=1,cpus=1 \
>>>>  -numa mem,size=1024M,policy=interleave,host-nodes=1
>>>
>>> What nodes would the memory be in, for this command line?  Does it just
>>
>> The original concept here is that if the nodeid is omitted, it will be
>> set node by node from node0. Here I also keep the original concept, so the
>> memory will be in node0 and node1.
>>
>>> compute the total and split it evenly across the nodes (so that the
>>> "-numa node" options could omit nodeid and cpus too)?
>>
>> If no memory size is given for any nodes, the memory will split across
>> all nodes like (ram_size / nb_numa_nodes). And yes nodeid and cpus options
>> can also be omitted from the original concept.
>>
>>>
>>> Also, do you still need a "-m" option if you use "-numa mem"?
>>
>> The "-m" options will be used to compute the memory size of each node
>> if the memory size of each node is not set by "-numa mem" option. This
>> is also be consistent with the original concept.
> 
> Ok.  You didn't answer my exact question though---could you run the
> above command line without "-m 2048"?

Sorry :(
Sure not. And if the memory size assigned by "-m" option is not equal
the total memory size assigned by "-numa mem,", the ACPI will write the
wrong table, then the guest kernel will detect this and ignore the wrong
ACPI numa table and assume that all of the memory are belong to one node.

Would you like to run without "-m" option in mind?

Thanks,
Wanlong Gao

> 
> (Of course with hotplug like in Igor's case you'll still need "-m
> maxmem=4096,slots=4" or something like that)
> 
> Paolo
> 

  reply	other threads:[~2013-08-21  9:09 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-20  1:07 [Qemu-devel] [PATCH V8 00/11] Add support for binding guest numa nodes to host numa nodes Wanlong Gao
2013-08-20  1:07 ` [Qemu-devel] [PATCH V8 01/11] NUMA: add NumaOptions, NumaNodeOptions and NumaMemOptions Wanlong Gao
2013-08-21 20:59   ` Eric Blake
2013-08-22  1:12     ` Wanlong Gao
2013-08-22  2:29       ` Eric Blake
2013-08-22  3:16         ` Wanlong Gao
2013-08-22  8:46           ` Laszlo Ersek
2013-08-22 16:14             ` Eric Blake
2013-08-22 16:36               ` Laszlo Ersek
2013-08-22 19:21         ` Paolo Bonzini
2013-08-20  1:07 ` [Qemu-devel] [PATCH V8 02/11] NUMA: split -numa option Wanlong Gao
2013-08-20  1:07 ` [Qemu-devel] [PATCH V8 03/11] NUMA: move numa related code to numa.c Wanlong Gao
2013-08-20  1:07 ` [Qemu-devel] [PATCH V8 04/11] NUMA: Add numa_info structure to contain numa nodes info Wanlong Gao
2013-08-20  1:07 ` [Qemu-devel] [PATCH V8 05/11] NUMA: Add Linux libnuma detection Wanlong Gao
2013-08-20  1:07 ` [Qemu-devel] [PATCH V8 06/11] NUMA: parse guest numa nodes memory policy Wanlong Gao
2013-08-20  1:07 ` [Qemu-devel] [PATCH V8 07/11] NUMA: set " Wanlong Gao
2013-08-20 13:41   ` Andrew Jones
2013-08-21  2:43     ` Wanlong Gao
2013-08-21  7:15       ` Andrew Jones
2013-08-21  7:23         ` Wanlong Gao
2013-08-20  1:07 ` [Qemu-devel] [PATCH V8 08/11] NUMA: add qmp command set-mem-policy to set memory policy for NUMA node Wanlong Gao
2013-08-20  1:07 ` [Qemu-devel] [PATCH V8 09/11] NUMA: add hmp command set-mem-policy Wanlong Gao
2013-08-20  1:07 ` [Qemu-devel] [PATCH V8 10/11] NUMA: add qmp command query-numa Wanlong Gao
2013-08-20  1:07 ` [Qemu-devel] [PATCH V8 11/11] NUMA: convert hmp command info_numa to use qmp command query_numa Wanlong Gao
2013-08-20 13:43 ` [Qemu-devel] [PATCH V8 00/11] Add support for binding guest numa nodes to host numa nodes Paolo Bonzini
2013-08-21  1:22   ` Wanlong Gao
2013-08-21  9:00     ` Paolo Bonzini
2013-08-21  9:08       ` Wanlong Gao [this message]
2013-08-21  9:22         ` Paolo Bonzini
2013-08-21  9:34           ` Wanlong Gao
2013-08-21 10:00             ` Paolo Bonzini
2013-08-21  9:33 ` Laszlo Ersek
2013-08-21  9:37   ` Wanlong Gao

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=5214838A.3090501@cn.fujitsu.com \
    --to=gaowanlong@cn.fujitsu.com \
    --cc=afaerber@suse.de \
    --cc=aliguori@us.ibm.com \
    --cc=bsd@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=hutao@cn.fujitsu.com \
    --cc=lcapitulino@redhat.com \
    --cc=lersek@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.huangpeng@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=y-goto@jp.fujitsu.com \
    /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).