From: xuehai zhang <hai@cs.uchicago.edu>
To: Mark Williamson <mark.williamson@cl.cam.ac.uk>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>, xen-devel@lists.xensource.com
Subject: Re: MPI benchmark performance gap between native linux anddomU
Date: Tue, 05 Apr 2005 17:39:32 -0500 [thread overview]
Message-ID: <425313A4.90609@cs.uchicago.edu> (raw)
In-Reply-To: <200504052334.09344.mark.williamson@cl.cam.ac.uk>
Mark,
Thanks for the advice. I will explicitly specify "cpu" option in domU's config file.
So far, I think my experiments are not affected by this. In my experiments, I only run at most 1
domU besides dom0. I think the domU will be assigned to 2nd CPU even the assignment policy is round
robin.
Xuehai
Mark Williamson wrote:
> On Tuesday 05 April 2005 23:29, xuehai zhang wrote:
>
>>>I did not specify "cpu" option in Xen's configuration file, so I think
>>>both dom0 and domU run on the same CPU (1st CPU). I will try to assign
>>>them to different CPUs later.
>>
>>I think I said something wrong here. If I do not specify "cpu" option in
>>Xen config file, I observe Xen usually assigns the 2nd CPU to domU while
>>running dom0 on the 1st CPU.
>
>
> Last time I looked, the default was to assign in a round robin fashion. i.e.
> the next domain you create will be on the 1st CPU (with dom0) unless you
> explicitly specify otherwise - watch out this doesn't confuse your testing.
>
> Cheers,
> Mark
>
next prev parent reply other threads:[~2005-04-05 22:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-04 23:30 MPI benchmark performance gap between native linux anddomU Ian Pratt
2005-04-04 23:43 ` xuehai zhang
2005-04-05 22:29 ` xuehai zhang
2005-04-05 22:34 ` Mark Williamson
2005-04-05 22:39 ` xuehai zhang [this message]
2005-04-05 22:43 ` Mark Williamson
2005-04-06 4:25 ` xuehai zhang
-- strict thread matches above, loose matches on Subject: below --
2005-04-05 2:07 Santos, Jose Renato G (Jose Renato Santos)
2005-04-05 8:59 ` Keir Fraser
2005-04-05 22:22 ` Nivedita Singhvi
2005-04-05 22:23 ` xuehai zhang
2005-04-05 22:34 ` xuehai zhang
2005-04-05 22:53 ` Nivedita Singhvi
2005-04-05 22:58 ` Nivedita Singhvi
2005-04-05 3:10 Santos, Jose Renato G (Jose Renato Santos)
2005-04-05 5:27 ` xuehai zhang
2005-04-05 15:23 Santos, Jose Renato G (Jose Renato Santos)
2005-04-05 15:47 ` Keir Fraser
2005-04-05 23:59 Santos, Jose Renato G (Jose Renato Santos)
2005-04-06 0:17 Santos, Jose Renato G (Jose Renato Santos)
2005-04-06 0:37 Santos, Jose Renato G (Jose Renato Santos)
2005-04-06 4:24 ` xuehai zhang
2005-04-06 7:08 Ian Pratt
2005-04-06 7:23 Ian Pratt
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=425313A4.90609@cs.uchicago.edu \
--to=hai@cs.uchicago.edu \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=mark.williamson@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.