From: "Daniel P. Berrange" <berrange@redhat.com>
To: Andrew Jones <drjones@redhat.com>
Cc: He Chen <he.chen@linux.intel.com>,
Eduardo Habkost <ehabkost@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v9] Allow setting NUMA distance for different NUMA nodes
Date: Thu, 27 Apr 2017 10:33:15 +0100 [thread overview]
Message-ID: <20170427093315.GI5346@redhat.com> (raw)
In-Reply-To: <20170427092715.s2tsewyxlpoumeyn@kamzik.brq.redhat.com>
On Thu, Apr 27, 2017 at 11:27:15AM +0200, Andrew Jones wrote:
> On Thu, Apr 27, 2017 at 10:35:58AM +0800, 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:
> >
> > #define MAX_NODES 128
> > #define NUMA_NODE_UNASSIGNED MAX_NODES
> > +#define NUMA_DISTANCE_MIN 10
> > +#define NUMA_DISTANCE_DEFAULT 20
> > +#define NUMA_DISTANCE_MAX 254
> > +#define NUMA_DISTANCE_UNREACHABLE 255
> > +# @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.
We should probably also document that @val must be greater than 10,
unless src == dst, in which case it must be equal to 10.
> > +#
> > +# Since: 2.10
> > +##
> > +{ 'struct': 'NumaDistOptions',
> > + 'data': {
> > + 'src': 'uint16',
> > + 'dst': 'uint16',
> > + 'val': 'uint8' }}
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-04-27 9:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 2:35 [Qemu-devel] [PATCH v9] Allow setting NUMA distance for different NUMA nodes He Chen
2017-04-27 9:21 ` Igor Mammedov
2017-04-27 9:27 ` Andrew Jones
2017-04-27 9:33 ` Daniel P. Berrange [this message]
2017-04-27 12:54 ` Eric Blake
2017-04-27 13:32 ` Igor Mammedov
2017-04-27 14:05 ` Markus Armbruster
2017-04-27 14:46 ` Igor Mammedov
2017-04-27 20:25 ` Eduardo Habkost
2017-04-28 9:39 ` He Chen
2017-04-28 9:55 ` 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=20170427093315.GI5346@redhat.com \
--to=berrange@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).