qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@hp.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 6/7] virtio-net: Add new RX filter controls
Date: Mon, 8 Jun 2009 14:18:07 -0600	[thread overview]
Message-ID: <7162ab20906081318g730eaf82pb526913b8b4c5d30@mail.gmail.com> (raw)
In-Reply-To: <4A2D63EC.9040003@codemonkey.ws>

On Mon, Jun 8, 2009 at 1:18 PM, Anthony Liguori<anthony@codemonkey.ws> wrote:
> Alex Williamson wrote:
>>
>> e1000 also allows the driver to selectively enable/disable RX of
>> packets to the broadcast address.  This is replicated with the
>> all/no-bcast options.  Finally, there may be cases where we want to
>> receive only unicast or only multicast address for special purpose
>> network devices.  This is provided by the nouni and nomulti options.
>> A proprietary guest know as DMX intends to make use of these extra
>> modes.  Are there any other interesting, useful and lightweight packet
>> filters we could implement?  Thanks,
>>
>
> I've been thinking about whether doing VLAN filtering/tagging within QEMU
> would make sense.  It could potentially simplify bridge setups tremendously.
>  Today, if you want to isolate VMs on separate vlans, it involves creating
> multiple bridges which gets ugly quickly.

IIRC, you have to be careful that the host NIC doesn't strip the VLAN
tag itself, which means you want the VLAN guests on a non-VLAN bridge.
 It's all rather confusing and I wouldn't be surprised if there's some
dependency on how much offloading the host NIC does.  We do have VLAN
filtering in virtio-net today, but of course it would be better if it
was done at a generic network level in QEMU or pushed deeper into the
host.  Tagging doesn't make much sense at the level we're doing it
now.

Alex

  parent reply	other threads:[~2009-06-08 20:18 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-05 20:46 [Qemu-devel] [PATCH 0/7] virtio-net: Filter cleanup/improvements Alex Williamson
2009-06-05 20:46 ` [Qemu-devel] [PATCH 1/7] virtio-net: Add version_id 7 placeholder for vnet header support Alex Williamson
2009-06-05 20:46 ` [Qemu-devel] [PATCH 2/7] virtio-net: Use a byte to store RX mode flags Alex Williamson
2009-06-05 20:47 ` [Qemu-devel] [PATCH 3/7] virtio-net: reorganize receive_filter() Alex Williamson
2009-06-05 20:47 ` [Qemu-devel] [PATCH 4/7] virtio-net: Fix MAC filter overflow handling Alex Williamson
2009-06-05 20:47 ` [Qemu-devel] [PATCH 5/7] virtio-net: MAC filter optimization Alex Williamson
2009-06-05 20:47 ` [Qemu-devel] [PATCH 6/7] virtio-net: Add new RX filter controls Alex Williamson
2009-06-06 20:48   ` Michael S. Tsirkin
2009-06-08 19:01     ` Alex Williamson
2009-06-08 19:18       ` Anthony Liguori
2009-06-08 19:29         ` Daniel P. Berrange
2009-06-08 21:03           ` Anthony Liguori
2009-06-09  9:57             ` Daniel P. Berrange
2009-06-09 15:00               ` Jamie Lokier
2009-06-09 15:42                 ` [Qemu-devel] " Jan Kiszka
2009-06-09 23:50                   ` Jamie Lokier
2009-06-10  8:46                   ` Michael S. Tsirkin
2009-06-10  8:58                     ` Jan Kiszka
2009-06-10  9:07                       ` Michael S. Tsirkin
2009-06-10  9:13                         ` Gleb Natapov
2009-06-10  9:17                           ` Michael S. Tsirkin
2009-06-10  9:22                             ` Gleb Natapov
2009-06-10  9:35                               ` Michael S. Tsirkin
2009-06-08 20:18         ` Alex Williamson [this message]
2009-06-05 20:47 ` [Qemu-devel] [PATCH 7/7] virtio-net: Increase filter and control limits Alex Williamson
2009-06-06 20:44   ` Michael S. Tsirkin
2009-06-08 18:49     ` Alex Williamson
2009-06-09 19:25 ` [Qemu-devel] [PATCH 0/7] virtio-net: Filter cleanup/improvements Mark McLoughlin
2009-06-09 21:08   ` Alex Williamson
2009-06-10  6:51   ` Rusty Russell
2009-06-10 20:43     ` Alex Williamson
2009-06-12 17:07     ` Mark McLoughlin
2009-06-12 19:19       ` 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=7162ab20906081318g730eaf82pb526913b8b4c5d30@mail.gmail.com \
    --to=alex.williamson@hp.com \
    --cc=anthony@codemonkey.ws \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).