From: Alex Williamson <alex.williamson@hp.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Rusty Russell <rusty@rustcorp.com.au>, kvm <kvm@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
Mark McLoughlin <markmc@redhat.com>
Subject: Re: [PATCH 0/2][RFC] virtio_net: MAC filtering
Date: Wed, 07 Jan 2009 11:28:25 -0700 [thread overview]
Message-ID: <1231352906.7109.140.camel@lappy> (raw)
In-Reply-To: <4964F11B.7020509@codemonkey.ws>
On Wed, 2009-01-07 at 12:14 -0600, Anthony Liguori wrote:
> Alex Williamson wrote:
> >
> > As noted in the RFC thread adding the kvm/qemu backing, this does
> > increase the size of the virtio-net device I/O port space, up to 1kB
> > with PCI rounding if we add a 4k entry VLAN bitmap. A 64 device limit
> > is still pretty high for a VM, but maybe we should think about adding
> > MMIO space for virtio-pci. Thanks,
> >
>
> I'm not quite sure the best way to address this. Maybe another control
> queue for sending commands to control this sort of stuff? What are your
> thoughts Rusty?
This is also a good time to decide if a fixed 16 entry MAC filter table
is sufficient. Should the size be programmed into the config space?
There's plenty of room to make it a bigger fixed size and still stay at
1kB of I/O port space with the VLAN table. This implementation is a
little wasteful of space in using 8 bytes to store the MAC and a valid
bit, but I suspect there's some endian issues I'm ignoring and a
standard data type might make that easier later.
Alex
--
Alex Williamson HP Open Source & Linux Org.
next prev parent reply other threads:[~2009-01-07 18:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 18:05 [PATCH 0/2][RFC] virtio_net: MAC filtering Alex Williamson
2009-01-07 18:14 ` Anthony Liguori
2009-01-07 18:28 ` Alex Williamson [this message]
2009-01-07 18:57 ` Anthony Liguori
2009-01-09 17:54 ` Avi Kivity
2009-01-13 21:23 ` [PATCH 0/4] " Alex Williamson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1231352906.7109.140.camel@lappy \
--to=alex.williamson@hp.com \
--cc=anthony@codemonkey.ws \
--cc=kvm@vger.kernel.org \
--cc=markmc@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).