All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Andre Przywara <andre.przywara@amd.com>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>,
	Juergen Gross <juergen.gross@ts.fujitsu.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH v8] Some automatic NUMA placement documentation
Date: Thu, 26 Jul 2012 18:09:59 +0200	[thread overview]
Message-ID: <1343318999.26725.7.camel@Abyss> (raw)
In-Reply-To: <20497.27009.964251.991072@mariner.uk.xensource.com>


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

On Thu, 2012-07-26 at 17:00 +0100, Ian Jackson wrote: 
> Dario Faggioli writes ("[PATCH v8] Some automatic NUMA placement documentation"):
> > About rationale, usage and (some small bits of) API.
> 
> > +Also, if `numa_placement` is set to `true`, the domain must not
> > +have any cpu affinity (i.e., `domain_build_info->cpumap` must
> > +have all its bits set, as it is by default), or domain creation
> > +will fail returning `ERROR_INVAL`.
> 
> This is no longer true, is it ?
> 
I think it is. Actually, it was you that suggested turning the code into
that... :-P

It's this thing I'm trying to document:

    if (libxl_defbool_val(info->numa_placement)) {
        int rc;

        if (!libxl_bitmap_is_full(&info->cpumap)) {
            LOG(ERROR, "Can run NUMA placement only if no vcpu "
                       "affinity is specified");
            return ERROR_INVAL;
        }

        rc = numa_place_domain(gc, domid, info);
        if (rc)
            return rc;
    }

Am I missing something?

> > +Analyzing various possible placement solutions is what makes the
> > +algorithm flexible and quite effective. However, that also means
> > +it won't scale well to systems with arbitrary number of nodes.
> > +For this reason, if machines with more than 16 NUMA nodes will
> > +ever exist, placement will automatically disables itself when
> > +running libxl on them.
> 
> This last is very awkwardly phrased.  How about:
> 
>    For this reason, automatic numa placement is disabled (with
>    a warning) if it is requested on a host with more than 16 NUMA
>    nodes.
> 
Fine with it. Will change it.

Dario

-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://retis.sssup.it/people/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

  reply	other threads:[~2012-07-26 16:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-26 15:46 [PATCH v8] Some automatic NUMA placement documentation Dario Faggioli
2012-07-26 16:00 ` Ian Jackson
2012-07-26 16:09   ` Dario Faggioli [this message]
2012-07-26 16:12     ` Ian Jackson

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=1343318999.26725.7.camel@Abyss \
    --to=dario.faggioli@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=andre.przywara@amd.com \
    --cc=juergen.gross@ts.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.