From: Max Krasnyansky <maxk@qualcomm.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: virtualization@lists.linux-foundation.org,
Brian Braunstein <linuxkernel@bristyle.com>,
Shaun Jackman <sjackman@gmail.com>,
netdev@vger.kernel.org, Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: Multicast and receive filtering in TUN/TAP
Date: Thu, 10 Jul 2008 19:20:07 -0700 [thread overview]
Message-ID: <4876C357.3030708@qualcomm.com> (raw)
In-Reply-To: <200807102223.40717.borntraeger@de.ibm.com>
Christian Borntraeger wrote:
> Am Donnerstag, 10. Juli 2008 schrieb Max Krasnyansky:
>>> Thing is, we are heading towards virtio.
>> Even for Windows ?
>
> Its possible:
> http://marc.info/?l=kvm&m=121075389300722&w=2
Nice.
btw Is there something similar for the display driver ? vmware has one.
>>> Unfortunately, virtio_net currently does not offer a method to register
> multicast addresses.
>> I haven't looked at the virtio stuff much, I was assuming that the host side
>> of it is still the TUN driver. Is it not ?
>
> Yes, the host side is still tun/tap. The problem is that qemu doesnt know
> which multicast addresses are used inside the guest.
Ah, now I see what you meant by virtio_net does not do multicast. I guess it
should trivial to add. Rusty will clarify it I guess.
Max
next prev parent reply other threads:[~2008-07-11 2:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 22:58 Multicast and receive filtering in TUN/TAP Max Krasnyansky
2008-07-10 8:29 ` Christian Borntraeger
2008-07-10 16:57 ` Max Krasnyansky
2008-07-10 20:23 ` Christian Borntraeger
2008-07-11 2:20 ` Max Krasnyansky [this message]
2008-07-11 7:01 ` Rusty Russell
2008-07-11 8:01 ` Max Krasnyansky
2008-07-10 21:38 ` Shaun Jackman
2008-07-11 2:32 ` Brian Braunstein
2008-07-11 3:05 ` Max Krasnyansky
2008-07-11 3:01 ` Max Krasnyansky
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=4876C357.3030708@qualcomm.com \
--to=maxk@qualcomm.com \
--cc=borntraeger@de.ibm.com \
--cc=linuxkernel@bristyle.com \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=sjackman@gmail.com \
--cc=virtualization@lists.linux-foundation.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).