WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] event priority

To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] event priority
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Mon, 10 Apr 2006 22:51:05 +0800
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 10 Apr 2006 07:51:33 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcZcq3HNhs6J9nPmTVWcPgHUFz6niAAAosCQ
Thread-topic: [Xen-devel] event priority
>From: Tian,Kevin
>Sent: 2006年4月10日 22:31
>
>Hi, Keir,
>       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 priority is
>decided completely by compilation sequence of different drivers?

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

Thanks,
Kevin

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

<Prev in Thread] Current Thread [Next in Thread>