From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH 0/5][RFC] virtio-net: MAC filtering
Date: Fri, 9 Jan 2009 11:56:07 -0800
Message-ID: <200901091156.08710.paul@codesourcery.com>
References: <1231349852.7109.79.camel@lappy> <200901091127.32987.paul@codesourcery.com> <4967A84E.9080908@codemonkey.ws>
Mime-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Cc: qemu-devel@nongnu.org, Alex Williamson <alex.williamson@hp.com>,
	kvm <kvm@vger.kernel.org>, Mark McLoughlin <markmc@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mail.codesourcery.com ([65.74.133.4]:41428 "EHLO
	mail.codesourcery.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752610AbZAIT4U (ORCPT <rfc822;kvm@vger.kernel.org>);
	Fri, 9 Jan 2009 14:56:20 -0500
In-Reply-To: <4967A84E.9080908@codemonkey.ws>
Content-Disposition: inline
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

> >> A concern here is the growing size of the virtio-net I/O port space
> >> config.  This series brings it up to 256 bytes with PCI resource
> >
> > This is one reason why IO ports are a reallybad idea. Use memory mapped
> > register spaces like any other sane system and you won't have a problem.
>
> IO ports are much faster for notification than MMIO in KVM which is why
> the space is currently IO ports.  It was never meant to hold very large
> amounts of data.

Huh, I'm surprised it makes any real difference. Other that initial setup, 
isn't it just used to "kick" the devieonce after new dscriptors have been 
added to the ring buffer? I'd expect to be a fairly expensive operation 
(bouncing back to userspace).

Paul