From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: Avi Kivity <avi@redhat.com>, Alexander Graf <agraf@suse.de>,
Anthony Liguori <anthony@codemonkey.ws>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH 0/3][RFC] NUMA: add host side pinning
Date: Fri, 25 Jun 2010 13:00:37 +0200 [thread overview]
Message-ID: <4C248C55.9020204@redhat.com> (raw)
In-Reply-To: <4C2342D1.4090103@amd.com>
On 06/24/10 13:34, Andre Przywara wrote:
> Avi Kivity wrote:
>> On 06/24/2010 01:58 PM, Andre Przywara wrote:
>> Non-anonymous memory doesn't work well with ksm and transparent
>> hugepages. Is it possible to use anonymous memory rather than file
>> backed?
> I'd prefer non-file backed, too. But that is how the current huge pages
> implementation is done. We could use MAP_HUGETLB and declare NUMA _and_
> huge pages as 2.6.32+ only. Unfortunately I didn't find an easy way to
> detect the presence of the MAP_HUGETLB flag. If the kernel does not
> support it, it seems that mmap silently ignores it and uses 4KB pages
> instead.
Bit behind on the mailing list, but I think this look very promising.
I really think it makes more sense to make QEMU aware of the NUMA setup
as well, rather than relying on numctl to do the work outside.
One thing you need to consider is what happens with migration once a
user specifies -numa. IMHO it is acceptable to simply disable migration
for the given guest.
Cheers,
Jes
PS: Are you planning on submitting anything to Linux Plumbers Conference
about this? :)
next prev parent reply other threads:[~2010-06-25 11:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 21:09 [PATCH 0/3][RFC] NUMA: add host side pinning Andre Przywara
2010-06-23 21:09 ` [PATCH 1/3] NUMA: add Linux libnuma detection Andre Przywara
2010-06-23 21:09 ` [PATCH 2/3] NUMA: add parsing of host NUMA pin option Andre Przywara
2010-06-23 21:09 ` [PATCH 3/3] NUMA: realize NUMA memory pinning Andre Przywara
2010-06-23 22:21 ` [PATCH 0/3][RFC] NUMA: add host side pinning Anthony Liguori
2010-06-23 22:29 ` Alexander Graf
2010-06-24 10:58 ` Andre Przywara
2010-06-24 11:12 ` Avi Kivity
2010-06-24 11:34 ` Andre Przywara
2010-06-24 11:42 ` Avi Kivity
2010-06-28 16:20 ` Anthony Liguori
2010-06-28 16:26 ` Alexander Graf
2010-06-29 9:46 ` Avi Kivity
2010-06-25 11:00 ` Jes Sorensen [this message]
2010-06-25 11:06 ` Andre Przywara
2010-06-25 11:37 ` Jes Sorensen
2010-06-28 16:17 ` Anthony Liguori
2010-06-29 9:48 ` Avi Kivity
2010-06-24 6:44 ` Andre Przywara
2010-06-24 13:14 ` Andi Kleen
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=4C248C55.9020204@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=agraf@suse.de \
--cc=andre.przywara@amd.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--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