xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dulloor <dulloor@gmail.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH 03/11] [XEN] NUMA guest tools interface
Date: Fri, 9 Apr 2010 00:58:38 -0400	[thread overview]
Message-ID: <o2r940bcfd21004082158yc381a255s3e6b6e95cdeccd0e@mail.gmail.com> (raw)
In-Reply-To: <4BBC76E2.9020603@amd.com>

On Wed, Apr 7, 2010 at 8:13 AM, Andre Przywara <andre.przywara@amd.com> wrote:
> Dulloor wrote:
>>
>> The patch adds hypercall interfaces to get/set the virtual numa layout
>> for a domain.
>
> I don't see the need for introducing this many new interfaces. I couldn't
> find a reference for the nodemap information (mfn_to_nid) to be actually
> used somewhere, is there any missing part or was it just for the sake of
> completeness?
The nodemap information is right now a place holder. The part is used in the
implementation of enlightened ballooning, which is essential for NUMA
guests that
could increase/decrease/exchange memory reservations. I will spin out
a refreshed
patch for this in a couple of days.

> Beside that, cpu_to_node is already in physinfo, and via xc_availheap (which
> takes a node parameter) you can query the amount of free memory per node. I
> think that is all we need to know about the host's NUMA topology, but
> correct me if I am wrong.
> (OK, the distance information is missing...)
I wanted to have all the desired node information (size, free memory,
node_to_cpu masks, distances) in a single place. But, I could have
constructed this without adding a new interface too.

> From a design point of view I would avoid exporting so many host machine
> information to Dom0 unless we really need it.
I agree. I am exporting only the information that is essential and
which makes design sense.

>
> Regards,
> Andre.
>
> --
> Andre Przywara
> AMD-Operating System Research Center (OSRC), Dresden, Germany
> Tel: +49 351 448-3567-12
>
>

      parent reply	other threads:[~2010-04-09  4:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-04 19:30 [PATCH 03/11] [XEN] NUMA guest tools interface Dulloor
2010-04-07 12:13 ` Andre Przywara
2010-04-07 14:52   ` Cui, Dexuan
2010-04-07 15:22     ` Keir Fraser
2010-04-09  5:14     ` Dulloor
2010-04-09  4:58   ` Dulloor [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=o2r940bcfd21004082158yc381a255s3e6b6e95cdeccd0e@mail.gmail.com \
    --to=dulloor@gmail.com \
    --cc=andre.przywara@amd.com \
    --cc=xen-devel@lists.xensource.com \
    /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).