All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: "Zhai, Edwin" <edwin.zhai@intel.com>
Cc: ryanh@us.ibm.com, xen-devel@lists.xensource.com
Subject: Re: [RFC][PATCH] domheap optimization for NUMA
Date: Wed, 02 Apr 2008 14:27:55 +0100	[thread overview]
Message-ID: <C419486B.1EB47%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <20080402130604.GH27634@edwin-srv.sh.intel.com>

On 2/4/08 14:06, "Zhai, Edwin" <edwin.zhai@intel.com> wrote:

> The issue is alloc_domheap_pages take domain* as parameter to indicate if need
> account pages for the domain, sometimes it's NULL. In this case, we can't
> deduct 
> the node from domain. I believe it's why use cpu here as getting cpuid is
> easier.

Yes, but it's a bad interface, particularlty when the function is called
alloc_domheap_pages_on_node(). Pass in a nodeid. Write a helper function to
work out the nodeid from the domain*.

> Another option, always use domain* to locate node(not allowed NULL) and add a
> new flag _MEMF_assign to indicate the assignment, which changes the interface
> and is invasive.

Yes, that's a bad idea.

 -- Keir

  reply	other threads:[~2008-04-02 13:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-31 10:40 [RFC][PATCH] domheap optimization for NUMA Zhai, Edwin
2008-03-31 10:47 ` Keir Fraser
2008-04-02 13:06   ` Zhai, Edwin
2008-04-02 13:27     ` Keir Fraser [this message]
2008-04-02 22:49       ` Andre Przywara
2008-04-02 23:21         ` Keir Fraser
2008-04-03 10:39           ` Andre Przywara
2008-04-03 10:58             ` Keir Fraser
2008-04-03 13:57               ` Andre Przywara
2008-04-03 14:49                 ` Keir Fraser
2008-04-04  8:37                 ` Isaku Yamahata
2008-04-04 13:22                 ` Aron Griffis
2008-04-07 13:25           ` Zhai, Edwin
2008-04-07 13:51             ` Keir Fraser

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=C419486B.1EB47%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=edwin.zhai@intel.com \
    --cc=ryanh@us.ibm.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 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.