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] more profiling

> In my experiments I also see overheads on issuing and revoking
> grants due to the use of atomic operations, but these are
> much less expensive than copying an entire packet as you
> do on the TX path. I am surprised with your results.
> Can you give more details about your configuration and how you
> are comparing the cost of copy versus issuing grants on TX.

I think you are right in saying that the issuing and revoking of grants
is due to the use of atomic operations. Having looked into it some more,
it looks like KeAcquireSpinlock (the windows lock operation) is fairly
expensive.

Under windows, it is the code that gets the next free ref that is
protected by spinlocks. I believe that if we only get the ref once, but
then reuse that ref over and over, then we'd get a lot better
performace.

James

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

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