From: Anthony Liguori <anthony@codemonkey.ws>
To: Andre Przywara <andre.przywara@amd.com>
Cc: qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>
Subject: [Qemu-devel] Re: [PATCH 4/8] v2: extend parser to parse pin: option
Date: Tue, 16 Dec 2008 18:19:18 -0600 [thread overview]
Message-ID: <49484586.7060106@codemonkey.ws> (raw)
In-Reply-To: <494838F1.6070005@amd.com>
Andre Przywara wrote:
> Anthony Liguori wrote:
>> Andre Przywara wrote:
>>> Signed-off-by: Andre Przywara <andre.przywara@amd.com>
>>>
>>
>> I think we suggested that this should be specified in a different
>> option than -numa to separate the host/guest configuration bits.
> As I said in the beginning of 0/8, I don't think that makes much sense.
> Do you want this to be independent of the rest of NUMA (guest) code?
> Then this is a different story.
I'm not sure I see what you're asking.
> The purpose of this code is to pin _multiple_ guest nodes to
> _multiple_ different host nodes, something that is quite intricate to
> do otherwise.
Right now, you say:
-numa 2,mem:1G;2G,cpu:0-1;2-3,pin:2;3
My most preferred syntax would be:
-numa node,mem=0G-1G,cpu=0-1,nodeid=0 -numa pin,nodeid=0,hostid=2 \
-numa node,mem=1G-3G,cpu=2-3,nodeid=1 -numa pin,nodeid=1,hostid=3
It's more typing, but it maps really well to how -net tap works and how
-drive works. It has a lot less special characters too. I'm not saying
this is the only right solution, but this is probably what I would do if
I were writing this.
>
> Please tell me your opinion (and maybe a concrete suggestion on which
> syntax to use).
>
> Regards,
> Andre.
>
> P.S. Do you agree to Avi that the colon should be substituted by an
> equal-sign?
>
Yes.
Regards,
Anthony Liguori
prev parent reply other threads:[~2008-12-17 0:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 14:17 [Qemu-devel] [PATCH 4/8] v2: extend parser to parse pin: option Andre Przywara
2008-12-16 21:17 ` [Qemu-devel] " Anthony Liguori
2008-12-16 23:25 ` Andre Przywara
2008-12-17 0:19 ` Anthony Liguori [this message]
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=49484586.7060106@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).