From: Anthony Liguori <anthony@codemonkey.ws>
To: Andre Przywara <andre.przywara@amd.com>
Cc: Avi Kivity <avi@redhat.com>, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH 2/3] NUMA: promoting NUMA topology to BIOS and pin guest memory
Date: Sat, 13 Dec 2008 17:42:13 -0600 [thread overview]
Message-ID: <49444855.3060605@codemonkey.ws> (raw)
In-Reply-To: <4943EE6C.8030508@amd.com>
Andre Przywara wrote:
> Avi Kivity wrote:
>> Anthony Liguori wrote:
>>>
>>> At this point, I'm okay with introducing the libnuma dependency for
>>> memory pinning. I'm not sure I think we should even present this as
>>> a command line option though. I think the command line option
>>> should just specify the NUMA topology and then we should use a
>>> monitor command for pinning (as you do on your next patch).
>>
>> It's helpful to have static pinning from the command line. That's
>> useful for quick tests for those of us who don't use management
>> interfaces.
>>
>> Since the monitor and command line can share code, there shouldn't be
>> any cost to this.
> ACK. Actually I'd had to add code to prevent pinning from the command
> line. I think this doesn't hurt, if you use virtualization for
> partitioning (where a NUMA architecture can actually help you, because
> guests don't compete will all other guests for the memory bandwidth),
> it is quite helpful to specify everything at the beginning.
The thing that makes me uneasy about it is the fact that it's part of
the base numa syntax. This combination of guest configuration and host
configuration seems less than optimal to me. This isn't something that
bothers me that much and won't keep me from applying the patches.
Regards,
Anthony Liguori
> Here even UP guest can take advantage:
> -numa 1,pin:1
>
> Regards,
> Andre.
>
next prev parent reply other threads:[~2008-12-13 23:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 11:29 [Qemu-devel] [PATCH 2/3] NUMA: promoting NUMA topology to BIOS and pin guest memory Andre Przywara
2008-12-12 15:01 ` [Qemu-devel] " Anthony Liguori
2008-12-13 9:42 ` Avi Kivity
2008-12-13 17:18 ` Andre Przywara
2008-12-13 23:42 ` Anthony Liguori [this message]
2008-12-14 7:27 ` Avi Kivity
2008-12-13 23:25 ` Andre Przywara
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=49444855.3060605@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=andre.przywara@amd.com \
--cc=avi@redhat.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).