xen-devel

[Top] [All Lists]

Re: [Xen-devel] event priority

from [Keir Fraser]

[Permanent Link][Original]

To:	"Tian, Kevin" <kevin.tian@xxxxxxxxx>
Subject:	Re: [Xen-devel] event priority
From:	Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date:	Mon, 10 Apr 2006 16:25:29 +0100
Cc:	xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date:	Mon, 10 Apr 2006 08:25:13 -0700
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
In-reply-to:	<571ACEFD467F7749BC50E0A98C17CDD8094E7ACF@pdsmsx403>
List-help:	<mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id:	Xen developer discussion <xen-devel.lists.xensource.com>
List-post:	<mailto:xen-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References:	<571ACEFD467F7749BC50E0A98C17CDD8094E7ACF@pdsmsx403>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx


On 10 Apr 2006, at 15:51, Tian, Kevin wrote:

        Seems current event priority is simple by
earlier-alloc-higher-priority style, because event ports are allocated
incrementally from 1 and event dispatcher uses bit search instruction
to walk pending events sequentially. Is there any plan (or benefit) to

add more flexible priority policy, since by current way the priorityis

decided completely by compilation sequence of different drivers?


Sorry, I should say driver init sequence here. :-)

If hardirq 'scheduling' is demonstrated to be an issue then we cancertainly work on this. There are various possible solutions -- theeasiest being to simply round-robin scan the event_pending array.


 -- Keir


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
[Xen-devel] event priority, Tian, Kevin RE: [Xen-devel] event priority, Tian, Kevin Re: [Xen-devel] event priority, Keir Fraser <= RE: [Xen-devel] event priority, Tian, Kevin

Previous by Date:	[Xen-devel] USB/IP in Xen, sanjay kumar
Next by Date:	Re: [Xen-devel] [PATCH]: kexec: framework and i386, Don Zickus
Previous by Thread:	RE: [Xen-devel] event priority, Tian, Kevin
Next by Thread:	RE: [Xen-devel] event priority, Tian, Kevin
Indexes:	[Date] [Thread] [Top] [All Lists]