[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <986656ee-37e9-0d99-3d1f-a48466ffe0ed@linux.vnet.ibm.com>
Date: Sat, 28 Jul 2018 14:07:20 +0530
From: Anshuman Khandual <khandual@...ux.vnet.ibm.com>
To: "Michael S. Tsirkin" <mst@...hat.com>
Cc: robh@...nel.org, srikar@...ux.vnet.ibm.com, aik@...abs.ru,
jasowang@...hat.com, linuxram@...ibm.com,
linux-kernel@...r.kernel.org,
virtualization@...ts.linux-foundation.org, hch@...radead.org,
paulus@...ba.org, joe@...ches.com, linuxppc-dev@...ts.ozlabs.org,
elfring@...rs.sourceforge.net, haren@...ux.vnet.ibm.com,
david@...son.dropbear.id.au
Subject: Re: [RFC 0/4] Virtio uses DMA API for all devices
On 07/27/2018 05:01 PM, Michael S. Tsirkin wrote:
> On Wed, Jul 25, 2018 at 08:56:23AM +0530, Anshuman Khandual wrote:
>> Results with and without the patches are similar.
>
> Thanks! And another thing to try is virtio-net with
> a fast NIC backend (40G and up). Unfortunately
> at this point loopback tests stress the host
> scheduler too much.
>
Sure. Will look around for a 40G NIC system. BTW I have been testing
virtio-net with a TAP device as back end.
ip tuntap add dev tap0 mode tap user $(whoami)
ip link set tap0 master virbr0
ip link set dev virbr0 up
ip link set dev tap0 up
which is exported into the guest as follows
-device virtio-net,netdev=network0,mac=52:55:00:d1:55:01 \
-netdev tap,id=network0,ifname=tap0,script=no,downscript=no \
But I have not run any network benchmarks on it though.
Powered by blists - more mailing lists