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] [Patch 2 of 2]: PV-domain SMP performance Linux-part

>>> "James Harper" <james.harper@xxxxxxxxxxxxxxxx> 16.01.09 12:01 >>>
>> You can pv up your Windows spinlocks in the block-instead-of-spin way
>> already (and yield-instead-of-spin is obviously even easier).
>> 
>
>But only in spinlocks that I 'own' completely right? I'm more concerned
>about spinlocks that I share with Windows (eg in NDIS).

As long as you can hook the respective OS interface (and you know it is
always used), you could do this on all spinlocks, since all that's needed is
logic in the acquire/release code (unless you want to add state to each
lock [like the spinning CPUs bitmap Keir mentioned], but that shouldn't
be necessary to achieve the intended effect).

Jan


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

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