Revert commit 03dd4642 "Avoid transmitting on the wrong CPU"

It severely impacts performance. The latency of waking up a different CPU
more than defeats the cost of one CPU blocking waiting on another.

Signed-off-by: Paul Durrant <paul.durrant@citrix.com>

diff --git a/src/xenvif/transmitter.c b/src/xenvif/transmitter.c
index b55daa3d5f48d58706b6d2f966f362b8d6e1dc7a..084ca76ca861ec2786472517ff6aaca97b3ac2d9 100644 (file)
--- a/src/xenvif/transmitter.c
+++ b/src/xenvif/transmitter.c
@@ -4008,9 +4008,7 @@ __TransmitterRingQueuePacket(
     // grab it then that's ok because whichever thread is holding it will have to call
     // __TransmitterRingReleaseLock() and will therefore drain the atomic packet list.
 
-    if (Ring->Index != KeGetCurrentProcessorNumberEx(NULL))
-        KeInsertQueueDpc(&Ring->Dpc, NULL, NULL);
-    else if (__TransmitterRingTryAcquireLock(Ring))
+    if (__TransmitterRingTryAcquireLock(Ring))
         __TransmitterRingReleaseLock(Ring);
 }