From: Zhigang Wang <zhigang.x.wang@oracle.com>
To: Mukesh Rathor <mukesh.rathor@oracle.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: increase evtchn limits
Date: Fri, 21 May 2010 13:07:42 +0800 [thread overview]
Message-ID: <4BF6151E.7050204@oracle.com> (raw)
In-Reply-To: <20100520204110.2d421bfe@mantra.us.oracle.com>
On 05/21/2010 11:41 AM, Mukesh Rathor wrote:
> Hi,
>
> I'm trying to boot up with lot more than 32 vcpus on this very large box.
> I overcame vcpu_info[MAX_VIRT_CPUS] by doing vcpu placement hypercall
> in guest, but now running into evt channel limit (lots of devices):
>
> unsigned long evtchn_pending[sizeof(unsigned long) * 8];
>
I'm not sure, but it seems: 1024 for 32bit and 4096 for 64bit.
32bit: 4 * (4 * 8) * 8 = 1024
64bit: 8 * (8 * 8) * 8 = 4096
zhigang
> which limits to 512 max for my 64bit dom0. The only recourse seems to
> create a new struct shared_info_v2{}, and re-arrange it a bit with lot
> more event channels. Since, start_info has magic with version info, I
> can just check that in guest and use new shared_info...(doing the design
> on the fly here). I can create a new vcpuop saying the guest is using
> newer version. Or forget new version of shared_info{}, I can just
> put evtchn stuff in my own mfn and tell hypervisor to relocate it,
> (just like vcpu_info does) via new VCPUOP_ call.
>
> Keir, what do you think?
>
> thanks,
> Mukesh
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-05-21 5:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 3:41 increase evtchn limits Mukesh Rathor
2010-05-21 5:07 ` Zhigang Wang [this message]
2010-05-21 7:12 ` Keir Fraser
2010-05-21 18:52 ` Mukesh Rathor
2010-05-21 20:15 ` Keir Fraser
2010-05-21 7:01 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2010-05-21 8:14 Jan Beulich
2010-05-21 9:25 ` Keir Fraser
2010-05-21 9:29 ` Keir Fraser
2010-05-21 11:09 ` Jan Beulich
2010-05-21 10:52 ` Jan Beulich
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=4BF6151E.7050204@oracle.com \
--to=zhigang.x.wang@oracle.com \
--cc=mukesh.rathor@oracle.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).