From: Paolo Bonzini <pbonzini@redhat.com>
To: gaowanlong@cn.fujitsu.com
Cc: qemu-devel <qemu-devel@nongnu.org>, ehabkost@redhat.com
Subject: Re: [Qemu-devel] QEMU NUMA and memory allocation problem
Date: Thu, 16 May 2013 14:02:11 +0200 [thread overview]
Message-ID: <5194CAC3.9040908@redhat.com> (raw)
In-Reply-To: <5194ABFD.8040200@cn.fujitsu.com>
Il 16/05/2013 11:50, Wanlong Gao ha scritto:
> To see that this 300M memory is allocated from host node0 again, but not host node1 as
> I expected.
>
> We think that QEMU can't handled this numa memory allocation well, and it will cause the
> cross node memory access performance regression.
>
> Any thoughts? Or, am I missing something?
Pinning memory to host NUMA nodes is not implemented. Something like
AutoNUMA would be able to balance the memory the right way.
Paolo
next prev parent reply other threads:[~2013-05-16 12:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 9:50 [Qemu-devel] QEMU NUMA and memory allocation problem Wanlong Gao
2013-05-16 12:02 ` Paolo Bonzini [this message]
2013-05-17 7:47 ` Wanlong Gao
2013-05-17 13:36 ` Eduardo Habkost
2013-05-20 2:03 ` Wanlong Gao
2013-05-20 2:03 ` Wanlong Gao
2013-05-20 3:03 ` Wanpeng Li
2013-05-20 3:03 ` Wanpeng Li
2013-05-20 3:03 ` Wanpeng Li
2013-05-20 3:03 ` Wanpeng Li
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=5194CAC3.9040908@redhat.com \
--to=pbonzini@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.