[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4B3211A3.1090202@redhat.com>
Date: Wed, 23 Dec 2009 14:48:35 +0200
From: Avi Kivity <avi@...hat.com>
To: Andi Kleen <andi@...stfloor.org>
CC: Ingo Molnar <mingo@...e.hu>,
Anthony Liguori <anthony@...emonkey.ws>,
Bartlomiej Zolnierkiewicz <bzolnier@...il.com>,
Gregory Haskins <gregory.haskins@...il.com>,
kvm@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org>,
torvalds@...ux-foundation.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
netdev@...r.kernel.org,
"alacrityvm-devel@...ts.sourceforge.net"
<alacrityvm-devel@...ts.sourceforge.net>,
Chris Wright <chrisw@...hat.com>
Subject: Re: [GIT PULL] AlacrityVM guest drivers for 2.6.33
On 12/23/2009 02:14 PM, Andi Kleen wrote:
>> http://www.redhat.com/f/pdf/summit/cwright_11_open_source_virt.pdf
>>
>> See slide 32. This is without vhost-net.
>>
> Thanks. Do you also have latency numbers?
>
No. Copying Chris. This was with the tx mitigation timer disabled, so
you won't see the usual atrocious userspace virtio latencies, but it
won't be as good as a host kernel implementation since we take a
heavyweight exit and qemu is pretty unoptimized.
> It seems like there's definitely still potential for improvement
> with messages<4K. But for the large messages they indeed
> look rather good.
>
There's still a lot of optimization to be done, but I hope this proves
there is nothing inherently slow about virtio.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists