From: Eric Blake <eblake@redhat.com>
To: He Chen <he.chen@linux.intel.com>, qemu-devel@nongnu.org
Cc: "Michael S . Tsirkin" <mst@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <rth@twiddle.net>,
Eduardo Habkost <ehabkost@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Andrew Jones <drjones@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v6] Allow setting NUMA distance for different NUMA nodes
Date: Tue, 11 Apr 2017 08:18:49 -0500 [thread overview]
Message-ID: <173a855f-1ca7-e680-a39c-c5e6bce310be@redhat.com> (raw)
In-Reply-To: <1491900566-32222-1-git-send-email-he.chen@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1785 bytes --]
On 04/11/2017 03:49 AM, He Chen wrote:
> This patch is going to add SLIT table support in QEMU, and provides
> additional option `dist` for command `-numa` to allow user set vNUMA
> distance by QEMU command.
>
> With this patch, when a user wants to create a guest that contains
> several vNUMA nodes and also wants to set distance among those nodes,
> the QEMU command would like:
>
> ```
> -numa node,nodeid=0,cpus=0 \
> -numa node,nodeid=1,cpus=1 \
> -numa node,nodeid=2,cpus=2 \
> -numa node,nodeid=3,cpus=3 \
> -numa dist,src=0,dst=1,val=21 \
> -numa dist,src=0,dst=2,val=31 \
> -numa dist,src=0,dst=3,val=41 \
> -numa dist,src=1,dst=2,val=21 \
> -numa dist,src=1,dst=3,val=31 \
> -numa dist,src=2,dst=3,val=21 \
> ```
>
> Signed-off-by: He Chen <he.chen@linux.intel.com>
> ---
Here is where you should mention what changed since v5, to help focus
the attention of reviewers that have read earlier versions.
> +++ b/qapi-schema.json
> ##
> +# @NumaDistOptions:
> +#
> +# Set the distance between 2 NUMA nodes.
> +#
> +# @src: source NUMA node.
> +#
> +# @dst: destination NUMA node.
> +#
> +# @val: NUMA distance from source node to destination node.
> +# When a node is unreachable from another node, set the distance
> +# between them to 255.
Still no mention that distances less than 10 are invalid, or that a node
to itself defaults to 10 and can't be changed, or that other distances
default to 20. But that starts to get complex enough, and you cover it
elsewhere, so I'm okay with what you have here.
Interface looks sane, but I'll leave others to do the code review.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2017-04-11 13:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 8:49 [Qemu-devel] [PATCH v6] Allow setting NUMA distance for different NUMA nodes He Chen
2017-04-11 12:21 ` Andrew Jones
2017-04-11 13:18 ` Eric Blake [this message]
2017-04-17 5:36 ` He Chen
2017-04-19 14:14 ` Igor Mammedov
2017-04-20 9:25 ` He Chen
2017-04-20 13:03 ` Igor Mammedov
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=173a855f-1ca7-e680-a39c-c5e6bce310be@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=drjones@redhat.com \
--cc=ehabkost@redhat.com \
--cc=he.chen@linux.intel.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).