search for: xmit_lock

Hello, I am using the IMQ with iptables (latest versions) and asking all packets to be enqueued to IMQ0 from both prerouting and postrouting (using different iptables rules to mark different streams). When I do this I get the kernel saying: "Dead loop on netdevice imq0, fix it urgently!" and communications stop intermittently. If I remove the jump from either preroute or postroute it

...e/net/core/dev.c Fri Feb 3 18:45:14 2006 >+++ b/linux-2.6-xen-sparse/net/core/dev.c Mon Feb 6 19:34:52 2006 >@@ -1206,76 +1206,16 @@ > return 0; > } > >-#define HARD_TX_LOCK(dev, cpu) { \ >- if ((dev->features & NETIF_F_LLTX) == 0) { \ >- spin_lock(&dev->xmit_lock); \ >- dev->xmit_lock_owner = cpu; \ >- } \ >-} >- >-#define HARD_TX_UNLOCK(dev) { \ >- if ((dev->features & NETIF_F_LLTX) == 0) { \ >- dev->xmit_lock_owner = -1; \ >- spin_unlock(&dev->xmit_lock); \ >- } \ >-} >- >-/** &gt...

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths

Unlike full virtualization in which the virtual machine provides the same platform interface as running natively on the hardware, paravirtualization requires modification to the guest operating system to work with the platform interface provided by the hypervisor. Xen was designed with performance in mind. Calls to the hypervisor are minimized, batched if necessary, and non-critical codepaths