From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LLN1V-00074R-38
	for qemu-devel@nongnu.org; Fri, 09 Jan 2009 14:28:01 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LLN1S-00072T-PQ
	for qemu-devel@nongnu.org; Fri, 09 Jan 2009 14:28:00 -0500
Received: from [199.232.76.173] (port=56042 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LLN1S-00072H-H8
	for qemu-devel@nongnu.org; Fri, 09 Jan 2009 14:27:58 -0500
Received: from mx20.gnu.org ([199.232.41.8]:55608)
	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 1LLN1S-0002z3-BD
	for qemu-devel@nongnu.org; Fri, 09 Jan 2009 14:27:58 -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 1LLN1Q-0001wE-6r
	for qemu-devel@nongnu.org; Fri, 09 Jan 2009 14:27:56 -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:27:32 -0800
References: <1231349852.7109.79.camel@lappy>
In-Reply-To: <1231349852.7109.79.camel@lappy>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200901091127.32987.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: qemu-devel@nongnu.org
Cc: Mark McLoughlin <markmc@redhat.com>, kvm <kvm@vger.kernel.org>, Alex Williamson <alex.williamson@hp.com>

> 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