Re: [libvirt] [RFC] NUMA topology specification

2011-09-01 Thread Bharata B Rao
On Tue, Aug 30, 2011 at 10:53 AM, Bharata B Rao bharata@gmail.com wrote: Hi, Here is another attempt at guest NUMA topology XML specification that should work for different NUMA topologies. Hi Daniel, Do you think I should go ahead and implement this ? Any comments or concerns ?

Re: [libvirt] [RFC] NUMA topology specification

2011-08-29 Thread Bharata B Rao
Hi, Here is another attempt at guest NUMA topology XML specification that should work for different NUMA topologies. We already specify the number of sockets, cores and threads a system has by using: cpu topology sockets='2' cores='2' threads='2' /cpu For NUMA, we can add the following: numa

Re: [libvirt] [RFC] NUMA topology specification

2011-08-24 Thread Bharata B Rao
On Tue, Aug 23, 2011 at 7:43 PM, Daniel P. Berrange berra...@redhat.com wrote: On Fri, Aug 19, 2011 at 12:05:43PM +0530, Bharata B Rao wrote: Hi, qemu supports specification of NUMA topology on command line using -numa option. -numa node[,mem=size][,cpus=cpu[-cpu]][,nodeid=node] I see

Re: [libvirt] [RFC] NUMA topology specification

2011-08-23 Thread Daniel P. Berrange
On Fri, Aug 19, 2011 at 12:05:43PM +0530, Bharata B Rao wrote: Hi, qemu supports specification of NUMA topology on command line using -numa option. -numa node[,mem=size][,cpus=cpu[-cpu]][,nodeid=node] I see that there is no way to specify such NUMA topology in libvirt XML. Are there

Re: [libvirt] [RFC] NUMA topology specification

2011-08-21 Thread Bharata B Rao
On Fri, Aug 19, 2011 at 7:10 PM, Adam Litke a...@us.ibm.com wrote: On 08/19/2011 01:35 AM, Bharata B Rao wrote: ... topology sockets='1' cores='2' threads='1' nodeid='0' cpus='0-1' mem='size' topology sockets='1' cores='2' threads='1' nodeid='1' cpus='2-3' mem='size' ... I like the idea of

[libvirt] [RFC] NUMA topology specification

2011-08-19 Thread Bharata B Rao
Hi, qemu supports specification of NUMA topology on command line using -numa option. -numa node[,mem=size][,cpus=cpu[-cpu]][,nodeid=node] I see that there is no way to specify such NUMA topology in libvirt XML. Are there plans to add support for NUMA topology specification ? Is anybody already

Re: [libvirt] [RFC] NUMA topology specification

2011-08-19 Thread Osier Yang
于 2011年08月19日 14:35, Bharata B Rao 写道: Hi, qemu supports specification of NUMA topology on command line using -numa option. -numa node[,mem=size][,cpus=cpu[-cpu]][,nodeid=node] I see that there is no way to specify such NUMA topology in libvirt XML. Are there plans to add support for NUMA

Re: [libvirt] [RFC] NUMA topology specification

2011-08-19 Thread Bharata B Rao
On Fri, Aug 19, 2011 at 12:55 PM, Osier Yang jy...@redhat.com wrote: 于 2011年08月19日 14:35, Bharata B Rao 写道: How about something like this ? (OPTION 1) cpu ... numa nodeid='node' cpus='cpu[-cpu]' mem='size' ... /cpu Libvirt already supported NUMA setting (both cpu and memory) on host

Re: [libvirt] [RFC] NUMA topology specification

2011-08-19 Thread Bharata B Rao
2011/8/19 Bharata B Rao bharata@gmail.com: Hence I am not sure if if numatune is the right place for defining host NUMA topology which btw should be independent of the host ^^guest Sorry for the typo. -- libvir-list mailing list libvir-list@redhat.com

Re: [libvirt] [RFC] NUMA topology specification

2011-08-19 Thread Osier Yang
于 2011年08月19日 16:09, Bharata B Rao 写道: On Fri, Aug 19, 2011 at 12:55 PM, Osier Yang jy...@redhat.com wrote: 于 2011年08月19日 14:35, Bharata B Rao 写道: How about something like this ? (OPTION 1) cpu ... numa nodeid='node' cpus='cpu[-cpu]' mem='size' ... /cpu Libvirt already supported NUMA

Re: [libvirt] [RFC] NUMA topology specification

2011-08-19 Thread Bharata B Rao
2011/8/19 Osier Yang jy...@redhat.com: Maybe something like: numatune guest .. /guest /numatune Yes, one possible solution. Let me wait and see what others say and what will be the consensus. Regards, Bharata. -- libvir-list mailing list libvir-list@redhat.com

Re: [libvirt] [RFC] NUMA topology specification

2011-08-19 Thread Adam Litke
On 08/19/2011 01:35 AM, Bharata B Rao wrote: May be something like this: (OPTION 2) cpu ... topology sockets='1' cores='2' threads='1' nodeid='0' cpus='0-1' mem='size' topology sockets='1' cores='2' threads='1' nodeid='1' cpus='2-3' mem='size' ... /cpu This should result in a 2 node