[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [RFC 00/13] numa: add '-numa cpu' option
|
From: |
Eduardo Habkost |
|
Subject: |
Re: [Qemu-devel] [RFC 00/13] numa: add '-numa cpu' option |
|
Date: |
Thu, 19 Jan 2017 08:55:27 -0200 |
|
User-agent: |
Mutt/1.7.1 (2016-10-04) |
On Thu, Jan 19, 2017 at 09:45:11AM +0000, Daniel P. Berrange wrote:
> On Wed, Jan 18, 2017 at 06:13:16PM +0100, Igor Mammedov wrote:
> >
> > Series introduces a new CLI option to allow mapping cpus to numa
> > nodes using public properties [socket|core|thread]-ids instead of
> > internal cpu-index and moving cpu<->node mapping from global bitmaps
> > to PCMachineState struct.
>
> What is the benefit of this change to apps ? Obviously libvirt uses
> the current syntax, but I'm not aware of what problems that has - why
> would libvirt want to use this new syntax instead ?
The current interface is based on a "CPU index", and the mapping
from CPU index to a specific CPU object can be non-trivial,
especially if "-device *-cpu", CPU hotplug, or more complex CPU
topologies are used.
--
Eduardo
- Re: [Qemu-devel] [RFC 09/13] numa: introduce '-numa cpu' cpu option, (continued)
- [Qemu-devel] [RFC 10/13] numa: replace cpu_index_to_socket_id() with cpu_index_to_instance_props(), Igor Mammedov, 2017/01/18
- [Qemu-devel] [RFC 11/13] numa: use new machine.cpu property with -numa cpus=... CLI, Igor Mammedov, 2017/01/18
- [Qemu-devel] [RFC 13/13] pc: cpu: make sure that cpu.node-id matches -numa mapping, Igor Mammedov, 2017/01/18
- [Qemu-devel] [RFC 12/13] pc: drop usage of legacy numa_get_node_for_cpu(), Igor Mammedov, 2017/01/18
- Re: [Qemu-devel] [RFC 00/13] numa: add '-numa cpu' option, Daniel P. Berrange, 2017/01/19
- Re: [Qemu-devel] [RFC 00/13] numa: add '-numa cpu' option, Igor Mammedov, 2017/01/20