From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Alex Williamson <alex.williamson@hp.com>,
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: Fri, 09 Jan 2009 19:54:12 +0200 [thread overview]
Message-ID: <49678F44.4090900@redhat.com> (raw)
In-Reply-To: <4964F11B.7020509@codemonkey.ws>
Anthony Liguori wrote:
> Alex Williamson wrote:
>> This series builds on some of the patches Mark McLoughlin has sent out
>> recently, so likely won't apply to any current trees until those get
>> upstream. The goal is to enable MAC filtering at the kvm/qemu level for
>> virtio-net packets. Promiscuous and allmulti mode are handled by adding
>> bits to Mark's proposed status field. I also add a 16 entry MAC table
>> for additional unicast and multicast addresses to filter. If this looks
>> reasonable, I'll follow-up with VLAN filtering.
>>
>> 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?
Reducing the amount of shared state will make maintaining compatibility
easier. A command queue introduces asynchronity and its associated
problems, but I think it's worthwhile.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2009-01-09 17:54 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
2009-01-07 18:57 ` Anthony Liguori
2009-01-09 17:54 ` Avi Kivity [this message]
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=49678F44.4090900@redhat.com \
--to=avi@redhat.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.