From: Keir Fraser <keir.xen@gmail.com>
To: Mukesh Rathor <mukesh.rathor@oracle.com>,
tupeng212 <tupeng212@gmail.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: alloc_heap_pages is low efficient with more CPUs
Date: Sat, 13 Oct 2012 07:03:30 +0100 [thread overview]
Message-ID: <CC9EC2C2.41A13%keir.xen@gmail.com> (raw)
In-Reply-To: <20121012153925.012846e4@mantra.us.oracle.com>
On 12/10/2012 23:39, "Mukesh Rathor" <mukesh.rathor@oracle.com> wrote:
> On Fri, 12 Oct 2012 20:24:16 +0800
> tupeng212 <tupeng212@gmail.com> wrote:
>
>> With 16 CPUs you find domain startup takes 3s always.
>> :No
>> With 16CPUs, first 0.3s, second 3s
>> With 64CPUs, first 3s, second 30s.
>>
>> With 64 CPUs you find it takes 3s first time, then 30s in future?
>> : Yes
>
> ...........
>
> I had seen this a while ago, it was always page scrubbing. That
> algoright was changed IIRC, so not sure if still could be the cause.
Tupeng,
If the tlbflush_filter() and cpumask_or() lines are commented out from the
if(need_tlbflush) block in alloc_heap_pages(), what are the domain creation
times like then? By the way it looks like you are not using xen-unstable or
xen-4.2, can you try with one of these later versions of Xen?
-- Keir
> My 2 cents,
> thanks
> Mukesh
next prev parent reply other threads:[~2012-10-13 6:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-11 15:18 alloc_heap_pages is low efficient with more CPUs tupeng212
2012-10-11 15:41 ` Keir Fraser
2012-10-12 12:24 ` tupeng212
2012-10-12 22:39 ` Mukesh Rathor
2012-10-13 6:03 ` Keir Fraser [this message]
2012-10-13 7:20 ` tupeng212
2012-10-13 8:59 ` Keir Fraser
[not found] <CC9EC91B.41A16%keir.xen@gmail.com>
2012-10-13 6:46 ` tupeng212
2012-10-13 8:59 ` Keir Fraser
2012-10-15 13:27 ` tupeng212
2012-10-15 15:45 ` Keir Fraser
2012-10-16 7:51 ` Jan Beulich
2012-10-16 8:03 ` Keir Fraser
2012-10-16 8:28 ` Jan Beulich
2012-10-16 8:53 ` 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=CC9EC2C2.41A13%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=mukesh.rathor@oracle.com \
--cc=tupeng212@gmail.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.