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:27:32 -0800
Message-ID: <200901091127.32987.paul@codesourcery.com>
References: <1231349852.7109.79.camel@lappy>
Mime-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Cc: Alex Williamson <alex.williamson@hp.com>,
	kvm <kvm@vger.kernel.org>, Mark McLoughlin <markmc@redhat.com>
To: qemu-devel@nongnu.org
Return-path: <kvm-owner@vger.kernel.org>
Received: from mail.codesourcery.com ([65.74.133.4]:46760 "EHLO
	mail.codesourcery.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751380AbZAIT1y (ORCPT <rfc822;kvm@vger.kernel.org>);
	Fri, 9 Jan 2009 14:27:54 -0500
In-Reply-To: <1231349852.7109.79.camel@lappy>
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
> rounding.  The VLAN filter bitmap would increase that by another 512
> bytes, making it 1kB and limiting us to something less than 64 such
> devices per guest.  Is anyone worried?  Should filter tables live in
> MMIO space for virtio devices?  I'll send out the guest side patches for
> virtio-net in a separate thread.  Thanks,

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.

Paul