From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LKcL6-0002Fb-Qf
	for qemu-devel@nongnu.org; Wed, 07 Jan 2009 12:37:08 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1LKcL4-0002EL-RV
	for qemu-devel@nongnu.org; Wed, 07 Jan 2009 12:37:08 -0500
Received: from [199.232.76.173] (port=33236 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1LKcL4-0002EG-O7
	for qemu-devel@nongnu.org; Wed, 07 Jan 2009 12:37:06 -0500
Received: from g1t0029.austin.hp.com ([15.216.28.36]:9228)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <alex.williamson@hp.com>) id 1LKcL4-0004UT-Dk
	for qemu-devel@nongnu.org; Wed, 07 Jan 2009 12:37:06 -0500
From: Alex Williamson <alex.williamson@hp.com>
Content-Type: text/plain
Date: Wed, 07 Jan 2009 10:37:32 -0700
Message-Id: <1231349852.7109.79.camel@lappy>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] [PATCH 0/5][RFC] virtio-net: MAC filtering
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: kvm <kvm@vger.kernel.org>, qemu-devel <qemu-devel@nongnu.org>
Cc: Mark McLoughlin <markmc@redhat.com>

This series is based on some of the work Mark McLoughlin has been doing,
so isn't going to apply until that makes it into the tree.  The goal is
to enable MAC filtering at the qemu/kvm level for virtio-net packets.  I
start by adding the capability to set the MAC address, naming the bits
in the status field, enabling filtering, and finally adding a MAC table
for additional MAC addresses.  If this looks reasonable, I'll follow up
with VLAN filtering support.

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,

Alex

-- 
Alex Williamson                             HP Open Source & Linux Org.