All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Harper <ryanh@us.ibm.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH 0/6] xen,xend,tools: NUMA support for Xen
Date: Tue, 11 Jul 2006 12:47:06 -0500	[thread overview]
Message-ID: <20060711174706.GN1694@us.ibm.com> (raw)
In-Reply-To: <86615345f6064a8e6b78321d3d8a7313@cl.cam.ac.uk>

* Keir Fraser <Keir.Fraser@cl.cam.ac.uk> [2006-07-11 10:59]:
> 
> On 11 Jul 2006, at 16:35, Ryan Harper wrote:
> 
> >Reposting the latest patches, no significant changes since May when I
> >last received feedback.  I've done some simple overhead and performance
> >numbers for these patches.
> >
> >Measuring NUMA allocator patch overhead via balloon driver and DOM0
> >involved starting DOM0 with all memory (4G) and ballooning down (256M)
> >as a starting point, [1]tracking the time it takes to balloon back up
> >to full memory.  The test was done with and without NUMA patches.
> 
> What sort of box are these numbers taken from? If it's not a NUMA 
> system then the slowdowns are rather poor. We're particularly 
> interested in not slowing down non-NUMA and small-NUMA (e.g., AMD K8) 
> x86 systems. They are what we really want to see measurements from.

The measurements are taken from a two-way Operton 248 (2.1Ghz) ,
small-NUMA.  I agree that there is significant overhead, however, we
aren't talking about fast path here; correct me if I'm wrong.   We
are only adding overhead to during domain startup.  The end result
being we pay for local memory allocation at creation time while
benefiting from local memory access for the lifetime of the domain.

I'm going to gather some oprofile data to see if I missed something
obvious, but in general I think that having local memory is of greater
benefit for the lifetime of a domain than the cost we incur during its
creation.

-- 
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253   T/L: 678-9253
ryanh@us.ibm.com

  reply	other threads:[~2006-07-11 17:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-11 15:35 [PATCH 0/6] xen,xend,tools: NUMA support for Xen Ryan Harper
2006-07-11 15:57 ` Keir Fraser
2006-07-11 17:47   ` Ryan Harper [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-11 16:40 Lu, Yinghai
2006-07-11 21:28 Ian Pratt
2006-07-12  1:23 ` Ryan Harper
2006-07-12 20:30   ` Ryan Harper

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=20060711174706.GN1694@us.ibm.com \
    --to=ryanh@us.ibm.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --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.