From: "Michael S. Tsirkin" <mst@redhat.com>
To: Vladislav Yasevich <vyasevich@gmail.com>
Cc: netdev@vger.kernel.org, jasowang@redhat.com,
Vladislav Yasevich <vyasevic@redhat.com>
Subject: Re: [PATCH] net: Resend IGMP memberships upon peer notification.
Date: Tue, 14 Mar 2017 18:36:22 +0200 [thread overview]
Message-ID: <20170314183318-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <1489496288-24139-1-git-send-email-vyasevic@redhat.com>
On Tue, Mar 14, 2017 at 08:58:08AM -0400, Vladislav Yasevich wrote:
> When we notify peers of potential changes, it's also good to update
> IGMP memberships. For example, during VM migration, updating IGMP
> memberships will redirect existing multicast streams to the VM at the
> new location.
>
> Signed-off-by: Vladislav Yasevich <vyasevic@redhat.com>
Seems to make sense
Acked-by: Michael S. Tsirkin <mst@redhat.com>
but I also think there's another problem: source does not
leave the groups on migration. So I think we should add code on the
host - it's snooping IGMPs so it should be able to leave groups on the
source when VM is disconnected.
> ---
> net/core/dev.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/net/core/dev.c b/net/core/dev.c
> index a229bf0..1ed927d 100644
> --- a/net/core/dev.c
> +++ b/net/core/dev.c
> @@ -1272,6 +1272,7 @@ void netdev_notify_peers(struct net_device *dev)
> {
> rtnl_lock();
> call_netdevice_notifiers(NETDEV_NOTIFY_PEERS, dev);
> + call_netdevice_notifiers(NETDEV_RESEND_IGMP, dev);
> rtnl_unlock();
> }
> EXPORT_SYMBOL(netdev_notify_peers);
> --
> 2.7.4
next prev parent reply other threads:[~2017-03-14 16:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 12:58 [PATCH] net: Resend IGMP memberships upon peer notification Vladislav Yasevich
2017-03-14 15:32 ` Michael S. Tsirkin
2017-03-14 16:36 ` Michael S. Tsirkin [this message]
2017-03-14 18:34 ` David Miller
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=20170314183318-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jasowang@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=vyasevic@redhat.com \
--cc=vyasevich@gmail.com \
/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).