xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel@lists.xenproject.org,
	Dario Faggioli <dario.faggioli@ctirix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [OSSTEST PATCH 1/2] TestSupport.pm: allow creating vNUMA enabled HVM guest configs
Date: Fri, 2 Oct 2015 14:02:15 +0200	[thread overview]
Message-ID: <1443787335.14525.62.camel@citrix.com> (raw)
In-Reply-To: <20151002113242.GA30122@zion.uk.xensource.com>


[-- Attachment #1.1: Type: text/plain, Size: 1953 bytes --]

On Fri, 2015-10-02 at 12:32 +0100, Wei Liu wrote:
> On Fri, Oct 02, 2015 at 01:17:31AM +0200, Dario Faggioli wrote:

> > diff --git a/Osstest/TestSupport.pm b/Osstest/TestSupport.pm
> > index 2b67e32..bf8bd56 100644
> > --- a/Osstest/TestSupport.pm
> > +++ b/Osstest/TestSupport.pm
> > @@ -1709,6 +1709,34 @@ sub prepareguest_part_xencfg ($$$$$) {

> > +        # Let's put all vnodes on pnode 0, as we don't even know
> > (for now)
> > +        # whether or not the host has more NUMA nodes than that!
> > +        @vnuma_pnode = (0) x $vnuma_nodes;
> > +
> 
> The thing I worry about putting everything in node 0 is that if we
> somehow has hardware that has several nodes but each node has
> relative
> small amount of ram it would cause this test case to fail.
> 
ISWYM.

> In the current arrangement, HVM guest gets 5G of ram if OSSTest
> determines the host has enough (2x5G + slack) ram for it.  So vnuma
> test
> case will fail on a box with 4 nodes but has 16G of ram. Is such
> hardware configuration not very likely to exist?
> 
Well, 16GB is a rather small amount of RAM for a box with 4 nodes, IMO.

However, I think your point is valid... I think I can, in case
vnuma_nodes is provided, overrun $ram_mb with something more likely to
fit on one physical node?

Unfortunately, it's not something we can check precisely, because, in
Xen, there is (yet) no mechanism to know, in case we have XX free RAM
(apart from parsing the console output after issuing `xl debug-key u',
which is really really unpractical!), how many of it actually comes
from each NUMA ndoe... but I can apply a bit of guessing.

What do you think?

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: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2015-10-02 12:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-01 23:17 [OSSTEST PATCH 0/2] Testcase for HVM vNUMA Dario Faggioli
2015-10-01 23:17 ` [OSSTEST PATCH 1/2] TestSupport.pm: allow creating vNUMA enabled HVM guest configs Dario Faggioli
2015-10-02 11:32   ` Wei Liu
2015-10-02 12:02     ` Dario Faggioli [this message]
2015-10-02 12:18       ` Wei Liu
2015-10-02 12:30         ` Dario Faggioli
2015-10-02 12:21       ` Wei Liu
2015-10-02 12:32         ` Dario Faggioli
2015-10-01 23:17 ` [OSSTEST PATCH 2/2] make-flight: create the vNUMA HVM test job Dario Faggioli
2015-10-05 16:34   ` Ian Jackson
2015-10-05 16:41     ` Wei Liu
2015-10-06  8:23       ` Ian Campbell
2015-10-06  8:33         ` Dario Faggioli
2015-10-06  9:03           ` Ian Campbell
2015-10-06  9:13             ` Dario Faggioli
2015-10-06  9:05           ` Wei Liu
2015-10-06  9:18             ` Ian Campbell
2015-10-09 14:42   ` Ian Campbell
2015-10-02  9:33 ` [OSSTEST PATCH 0/2] Testcase for HVM vNUMA Dario Faggioli
2015-10-02 10:15 ` Dario Faggioli
2015-10-02 11:40   ` Wei Liu

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=1443787335.14525.62.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=dario.faggioli@ctirix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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).