From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael S. Tsirkin" Subject: Re: vhost net: performance with ping benchmark Date: Tue, 25 Aug 2009 17:02:34 +0300 Message-ID: <20090825140234.GA14129@redhat.com> References: <20090824081240.GA3415@redhat.com> <20090824212137.GA9835@redhat.com> <4A934AF7.2090904@codemonkey.ws> <4A936525.5030300@redhat.com> <4A93E1DF.5080004@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Avi Kivity , virtualization@lists.linux-foundation.org, kvm@vger.kernel.org, Rusty Russell , Mark McLoughlin To: Anthony Liguori Return-path: Received: from mx1.redhat.com ([209.132.183.28]:50091 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754853AbZHYOEK (ORCPT ); Tue, 25 Aug 2009 10:04:10 -0400 Content-Disposition: inline In-Reply-To: <4A93E1DF.5080004@codemonkey.ws> Sender: kvm-owner@vger.kernel.org List-ID: On Tue, Aug 25, 2009 at 08:06:39AM -0500, Anthony Liguori wrote: > Avi Kivity wrote: >>> I think this is likely going to be needed regardless. I also think >>> the tap compatibility suggestion would simplify the consumption of >>> this in userspace. >> >> What about veth pairs? > > Does veth support GSO and checksum offload? AFAIK, no. But again, improving veth is a separate project :) >>> I'd like some time to look at get_state/set_state ioctl()s along with >>> dirty tracking support. It's a much better model for live migration >>> IMHO. >> >> My preference is ring proxying. Not we'll need ring proxying (or at >> least event proxying) for non-MSI guests. > > I avoided suggested ring proxying because I didn't want to suggest that > merging should be contingent on it. Happily, the proposed interface supports is. > Regards, > > Anthony Liguori