From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: increase evtchn limits Date: Fri, 21 May 2010 12:09:12 +0100 Message-ID: <4BF685F802000078000037C5@vpn.id2.novell.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser , "mukesh.rathor@oracle.com" Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org >>> On 21.05.10 at 11:29, Keir Fraser wrote: > On 21/05/2010 10:25, "Keir Fraser" wrote: >=20 >>> There are 5 event channels per CPU (timer, reschedule IPI, SMP call = function >>> IPI, SMP call function single IPI, and spinlock wakeup IPI). >=20 >=20 > 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