From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Zhigang Wang <zhigang.x.wang@oracle.com>,
xen-devel <xen-devel@lists.xensource.com>
Subject: Re: increase evtchn limits
Date: Fri, 21 May 2010 11:52:14 -0700 [thread overview]
Message-ID: <20100521115214.47b18afe@mantra.us.oracle.com> (raw)
In-Reply-To: <C81BF0DD.14D78%keir.fraser@eu.citrix.com>
On Fri, 21 May 2010 08:12:13 +0100
Keir Fraser <keir.fraser@eu.citrix.com> wrote:
> On 21/05/2010 06:07, "Zhigang Wang" <zhigang.x.wang@oracle.com> wrote:
>
> >> 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
>
> This is correct. Which is why I wonder how many CPUs you are dealing
> with, and how many event channels are being allocated per CPU. 4096
> event channels ought to be plenty for dom0 bringup on even a very big
> system.
>
> K.
>
My bad, it's ulong[], not sure why I thought it was uchar[]. So sorry
for the false alarm. I'm hitting BUG_ON(!test_bit(chn, s->evtchn_mask));
in bind_evtchn_to_cpu() and when I saw it on chn == 520, combined with
my thinking it was uchar, i made wrong conclusion. Apologies. Anyways,
I'll debug further.
But looking forward, I can see hitting limits of 4096 not too far in
future, so I think it will be a great idea to 'collapse the four IPIs
onto one event channel', perhaps next xen release.
Thanks again.
Mukesh
next prev parent reply other threads:[~2010-05-21 18:52 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
2010-05-21 7:12 ` Keir Fraser
2010-05-21 18:52 ` Mukesh Rathor [this message]
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=20100521115214.47b18afe@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
--cc=zhigang.x.wang@oracle.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).