From: Dario Faggioli <dario.faggioli@citrix.com>
To: Saurabh Mishra <saurabh.globe@gmail.com>
Cc: xen-devel@lists.xen.org
Subject: Re: Xen NUMA memory allocation policy
Date: Fri, 20 Dec 2013 14:52:44 +0100 [thread overview]
Message-ID: <1387547564.23792.45.camel@Solace> (raw)
In-Reply-To: <CAMnwyJ2JM0EZqZbY6DC=va=g6GQEEVkqm5kZtH3x2g12X4CwJA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1727 bytes --]
On gio, 2013-12-19 at 15:48 -0800, Saurabh Mishra wrote:
> Hi Dario --
>
Hi,
> >Mmm... BTW, if I can ask, what's the config file for these domains?
>
> Here's the config file :-
>
>
> name = "hvm-vm6"
> boot = "c"
> memory = 98304
> vcpus = 32
> disk = [ 'file:<image,hda,w' ]
> vif = [ 'model=e1000, mac=06:00:00:00:00:00, bridge=br0',
> 'model=e1000, mac=06:00:01:00:00:00, bridge=br1' ]
> pci = [ '0000:07:10.0=0@0a', '0000:07:10.2=0@0b',
> '0000:07:10.4=0@0c', '0000:07:10.6=0@0d', '0000:07:11.0=0@0e',
> '0000:07:11.2=0@0f', '0000:07:10.1=0@10', '0000:07:10.3=0@11',
> '0000:07:10.5=0@12', '0000:07:10.7=0@13', '0000:07:11.1=0@14',
> '0000:88:10.0=0@15', '0000:88:10.2=0@16', '0000:88:10.4=0@17
> ', '0000:88:10.6=0@18', '0000:88:11.0=0@19', '0000:88:11.2=0@1a',
> '0000:88:10.1=0@1b', '0000:88:10.3=0@1c', '0000:88:10.5=0@1d',
> '0000:88:10.7=0@1e', '0000:88:11.1=0@1f' ]
> cpus = [ '4', '5', '6', '7', '8', '9', '10', '11', '12', '13', '14',
> '15', '16', '17', '18', '19', '20', '21', '22', '23', '24', '25',
> '26', '27', '28', '29', '30', '31', '32', '33', '34', '35' ]
>
Ok. The reason why I asked was that I was seeing you the memory for the
domain being allocated from multiple NUMA node, which is what happens by
default, so I was wondering whether there could be preblems somewhere...
However, now I see that that's because of this line above, pinning cpus
at creation time.
Thanks and Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2013-12-20 13:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 19:41 Xen NUMA memory allocation policy Saurabh Mishra
2013-12-18 1:38 ` Dario Faggioli
2013-12-19 23:48 ` Saurabh Mishra
2013-12-20 13:52 ` Dario Faggioli [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=1387547564.23792.45.camel@Solace \
--to=dario.faggioli@citrix.com \
--cc=saurabh.globe@gmail.com \
--cc=xen-devel@lists.xen.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).