Re: [net-next V3 0/2] drivers: net: virtio_net: implement

2019-11-26 Thread David Miller
net-next is closed ___ Virtualization mailing list Virtualization@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/virtualization

[net-next V3 0/2] drivers: net: virtio_net: implement

2019-11-26 Thread Julio Faracco
This series add two important features. One of them changes the .ndo_tx_timeout to include an extra parameter to identify the stuck queue. Many drivers are using a nester loop to identify which queue is stooped/stucked. This is a redundant work since dev_watchdog is doing exactly the same thing.

[net-next V3 2/2] drivers: net: virtio_net: Implement a dev_watchdog handler

2019-11-26 Thread Julio Faracco
Driver virtio_net is not handling error events for TX provided by dev_watchdog. This event is reached when transmission queue is having problems to transmit packets. This could happen for any reason. To enable it, driver should have .ndo_tx_timeout implemented. This commit brings back

Re: [PATCH 1/1] virtio_ring: fix return code on DMA mapping fails

2019-11-26 Thread Christoph Hellwig
On Sat, Nov 23, 2019 at 09:39:08AM -0600, Tom Lendacky wrote: > Ideally, having a pool of shared pages for DMA, outside of standard > SWIOTLB, might be a good thing. On x86, SWIOTLB really seems geared > towards devices that don't support 64-bit DMA. If a device supports 64-bit > DMA then it can