From mboxrd@z Thu Jan  1 00:00:00 1970
From: Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: [PATCH] kvm tools: Implement virtio network device
Date: Wed, 13 Apr 2011 14:51:17 +0300
Message-ID: <4DA58E35.5010801@cs.helsinki.fi>
References: <1302695328-3503-1-git-send-email-asias.hejun@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Cyrill Gorcunov <gorcunov@gmail.com>, Ingo Molnar <mingo@elte.hu>,
	kvm@vger.kernel.org
To: Asias He <asias.hejun@gmail.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from courier.cs.helsinki.fi ([128.214.9.1]:57286 "EHLO
	mail.cs.helsinki.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752478Ab1DMLvU (ORCPT <rfc822;kvm@vger.kernel.org>);
	Wed, 13 Apr 2011 07:51:20 -0400
In-Reply-To: <1302695328-3503-1-git-send-email-asias.hejun@gmail.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On 4/13/11 2:48 PM, Asias He wrote:
> This patch implement virtio network device.
> Use '-n virtio or --network=virtio' to enable it.
>
> The current implementation uses tap which needs root privileges to create a
> virtual network device (tap0) on host side. Actually, what we need is
> CAP_NET_ADMIN.
>
> The host side tap0 is set to 192.168.33.2/24.
> You need to configure the guest side eth0 to any ip address in
> 192.168.33.0/24.
>
> Here are some scp performance test for differenct implementations:
> None of rx and tx as thread:
> guest to host 3.2MB/s
> host  to guest 3.1MB/s
>
> Only rx as thread:
> guest to host  14.7MB/s
> host  to guest 33.4MB/s
>
> Both rx and tx as thread(This patch works this way):
> guest to host  19.8MB/s
> host  to guest 32.5MB/s
>
> Signed-off-by: Asias He<asias.hejun@gmail.com>

This is already in master. Thanks!