From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LLNSy-0003Ur-Dl
	for qemu-devel@nongnu.org; Fri, 09 Jan 2009 14:56:24 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LLNSw-0003Ue-Bm
	for qemu-devel@nongnu.org; Fri, 09 Jan 2009 14:56:23 -0500
Received: from [199.232.76.173] (port=58387 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LLNSw-0003Ub-68
	for qemu-devel@nongnu.org; Fri, 09 Jan 2009 14:56:22 -0500
Received: from mx20.gnu.org ([199.232.41.8]:57064)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <paul@codesourcery.com>)
	id 1LLNSv-0000cz-P6
	for qemu-devel@nongnu.org; Fri, 09 Jan 2009 14:56:21 -0500
Received: from mail.codesourcery.com ([65.74.133.4])
	by mx20.gnu.org with esmtp (Exim 4.60)
	(envelope-from <paul@codesourcery.com>) id 1LLNSu-0003OC-Ay
	for qemu-devel@nongnu.org; Fri, 09 Jan 2009 14:56:20 -0500
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
References: <1231349852.7109.79.camel@lappy>
	<200901091127.32987.paul@codesourcery.com>
	<4967A84E.9080908@codemonkey.ws>
In-Reply-To: <4967A84E.9080908@codemonkey.ws>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200901091156.08710.paul@codesourcery.com>
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Mark McLoughlin <markmc@redhat.com>, qemu-devel@nongnu.org, Alex Williamson <alex.williamson@hp.com>, kvm <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