From: "Jan Beulich" <JBeulich@novell.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>,
"mukesh.rathor@oracle.com" <mukesh.rathor@oracle.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: increase evtchn limits
Date: Fri, 21 May 2010 12:09:12 +0100 [thread overview]
Message-ID: <4BF685F802000078000037C5@vpn.id2.novell.com> (raw)
In-Reply-To: <C81C10EF.14D8A%keir.fraser@eu.citrix.com>
>>> On 21.05.10 at 11:29, Keir Fraser <keir.fraser@eu.citrix.com> wrote:
> On 21/05/2010 10:25, "Keir Fraser" <keir.fraser@eu.citrix.com> wrote:
>
>>> There are 5 event channels per CPU (timer, reschedule IPI, SMP call function
>>> IPI, SMP call function single IPI, and spinlock wakeup IPI).
>
>
> It would be very easy to collapse the four IPIs onto one event channel plus
> a bitmask of IPI reasons. Then that would be a much more economical two
> event channels per CPU. And the change is a hell of a lot easier to
> implement than extensible event channels. I bet it could be knocked together
> in an hour.
Indeed, it didn't occur to me to do it that way, but this sounds pretty
strait forward to implement.
Thanks, Jan
next prev parent reply other threads:[~2010-05-21 11:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 8:14 increase evtchn limits Jan Beulich
2010-05-21 9:25 ` Keir Fraser
2010-05-21 9:29 ` Keir Fraser
2010-05-21 11:09 ` Jan Beulich [this message]
2010-05-21 10:52 ` Jan Beulich
-- strict thread matches above, loose matches on Subject: below --
2010-05-21 3:41 Mukesh Rathor
2010-05-21 5:07 ` Zhigang Wang
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
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=4BF685F802000078000037C5@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=keir.fraser@eu.citrix.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).