From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: yue <ooolinux@163.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: how many phy cpus shoulf assigned to dom0
Date: Wed, 4 May 2011 09:18:54 -0400 [thread overview]
Message-ID: <20110504131854.GB19769@dumpdata.com> (raw)
In-Reply-To: <6441b353.11596.12fb9ca1050.Coremail.ooolinux@163.com>
On Wed, May 04, 2011 at 02:55:18PM +0800, yue wrote:
> how many phy cpus shoulf assigned to dom0
That depends. I am actually running with all cpus, but then this is development machines.
In production I think the idea is one or two - depending on your workload.
>
> thanks
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-05-04 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 6:55 how many phy cpus shoulf assigned to dom0 yue
2011-05-04 13:18 ` Konrad Rzeszutek Wilk [this message]
2011-05-04 16:18 ` Joseph Glanville
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=20110504131854.GB19769@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=ooolinux@163.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).