search for: ckt15

...t_rxtx.c and consider adding a hardware memory barrier between writing used->idx and reading avail->flags. Cheers, -Luke P.S. I notice that the Linux virtio-net driver does not seem to tolerate spurious interrupts, even though the Virtio 1.0 spec requires this ("must"). On 3.13.11-ckt15 I see them trigger an "irq nobody cared" kernel log message and then the irq is disabled. If that sounds suspicious I can supply more information. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linuxfoundation.org/pipermail/virtualization/...

...t_rxtx.c and consider adding a hardware memory barrier between writing used->idx and reading avail->flags. Cheers, -Luke P.S. I notice that the Linux virtio-net driver does not seem to tolerate spurious interrupts, even though the Virtio 1.0 spec requires this ("must"). On 3.13.11-ckt15 I see them trigger an "irq nobody cared" kernel log message and then the irq is disabled. If that sounds suspicious I can supply more information. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linuxfoundation.org/pipermail/virtualization/...

...e memory > barrier between writing used->idx and reading avail->flags. > > Cheers, > -Luke > > P.S. I notice that the Linux virtio-net driver does not seem to tolerate > spurious interrupts, even though the Virtio 1.0 spec requires this > ("must"). On 3.13.11-ckt15 I see them trigger an "irq nobody cared" kernel > log message and then the irq is disabled. If that sounds suspicious I can > supply more information. > >

...used->idx and reading avail->flags. > > Cheers, > -Luke I agree, this looks like a bug in dpdk. > P.S. I notice that the Linux virtio-net driver does not seem to tolerate > spurious interrupts, even though the Virtio 1.0 spec requires this ("must"). On > 3.13.11-ckt15 I see them trigger an "irq nobody cared" kernel log message and > then the irq is disabled. If that sounds suspicious I can supply more > information. > > More information might be useful, yes. Just guessing from the available info: I think you refer to this: The d...

Hi Nikolay, I poked at src/lib/virtio/virtq.lua a bit - I was surprised to find no explicit CPU memory barriers in the virtq implementation. These are typically required when using virtio on smp machines - the spec actually mention where barriers are necessary. Are the barriers implicit somehow for lua? I'd be curious to learn. Thanks, -- MST

Hi Nikolay, I poked at src/lib/virtio/virtq.lua a bit - I was surprised to find no explicit CPU memory barriers in the virtq implementation. These are typically required when using virtio on smp machines - the spec actually mention where barriers are necessary. Are the barriers implicit somehow for lua? I'd be curious to learn. Thanks, -- MST