From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@redhat.com>
Subject: Re: KVM performance vs. Xen
Date: Thu, 30 Apr 2009 16:53:47 +0300
Message-ID: <49F9AD6B.3050300@redhat.com>
References: <49F8672E.5080507@linux.vnet.ibm.com> <49F967AE.4040905@redhat.com> <49F9AB64.20506@codemonkey.ws>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Andrew Theurer <habanero@linux.vnet.ibm.com>,
	kvm-devel <kvm@vger.kernel.org>
To: Anthony Liguori <anthony@codemonkey.ws>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx2.redhat.com ([66.187.237.31]:45568 "EHLO mx2.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1756308AbZD3Nxx (ORCPT <rfc822;kvm@vger.kernel.org>);
	Thu, 30 Apr 2009 09:53:53 -0400
In-Reply-To: <49F9AB64.20506@codemonkey.ws>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Anthony Liguori wrote:
>
>>> 2) cpu_physical_memory_rw due to not using preadv/pwritev?
>>
>> I think both virtio-net and virtio-blk use memcpy().
>
> With latest linux-2.6, and a development snapshot of glibc, virtio-blk 
> will not use memcpy() anymore but virtio-net still does on the receive 
> path (but not transmit).

There's still the kernel/user copy, so we have two copies on rx, one on tx.

-- 
error compiling committee.c: too many arguments to function