From: Ryan Harper <ryanh@us.ibm.com>
To: xen-devel@lists.xensource.com
Subject: [PATCH 0/6] xen,xend,tools: Add NUMA support to Xen
Date: Mon, 31 Jul 2006 14:09:58 -0500 [thread overview]
Message-ID: <20060731190958.GI1694@us.ibm.com> (raw)
I've respun the NUMA patches against 10874 and I'm re-submitting them
with the optimizations mentioned [1]previously on the list. There was a
request to see the overhead on non-numa/single-node machines. I've
re-run those benchmarks (ballooning up from small mem to multi-gig) as
well as timing the initially domain increase_reservation time to gauge
the overhead when allocating from the heap.
The results for these were done on an x460, single node, with 6G ram.
The balloon test was from 512M to ~6G. The NUMA patches include all of
the previous optimizations.
Balloon Up:
Without NUMA With NUMA NUMA Delta
Try1: 2943ms 2937ms -6ms
Try2: 2996ms 2992ms -4ms
Try3: 2971ms 2968ms -3ms
Increase reservation
Without NUMA:
MemSize 128M 512M 1G 2G 3G 4G
------------------------------------------
Try1: 10ms 38ms 76ms 160ms 237ms 308ms
Try2: 9ms 37ms 76ms 151ms 232ms 308ms
Try3: 9ms 37ms 76ms 151ms 226ms 311ms
With NUMA:
MemSize 128M 512M 1G 2G 3G 4G
------------------------------------------
Try1: 10ms 42ms 84ms 170ms 260ms 346ms
Try2: 10ms 42ms 83ms 167ms 255ms 346ms
Try3: 10ms 42ms 83ms 168ms 251ms 346ms
The only other change has been to the infrastructure patch in which I
added the call to Xen's command line parsing to pick up the numa=
options. This allows even on NUMA systems to disable NUMA parsing and
fake the number of nodes (numa=off fake=1, would fake 1 node).
1. http://lists.xensource.com/archives/html/xen-devel/2006-07/msg00384.html
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253 T/L: 678-9253
ryanh@us.ibm.com
next reply other threads:[~2006-07-31 19:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 19:09 Ryan Harper [this message]
2006-08-01 7:46 ` [PATCH 0/6] xen,xend,tools: Add NUMA support to Xen Tristan Gingold
2006-08-01 15:40 ` Ryan Harper
2006-08-02 5:59 ` Tristan Gingold
2006-08-02 22:29 ` Ryan Harper
2006-08-03 6:05 ` Tristan Gingold
2006-08-05 0:33 ` [PATCH 0/6] xen, xend, tools: Add NUMA support to Xen Issues on the ES7000 Subrahmanian, Raj
2006-08-07 13:23 ` Ryan Harper
2006-08-07 19:29 ` Subrahmanian, Raj
2006-08-01 9:29 ` [PATCH 0/6] xen,xend,tools: Add NUMA support to Xen Tristan Gingold
2006-08-02 6:14 ` Tristan Gingold
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=20060731190958.GI1694@us.ibm.com \
--to=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.