All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Stevens <dlstevens@us.ibm.com>
To: David Miller <davem@davemloft.net>
Cc: fbl@redhat.com, herbert@gondor.hengli.com.au,
	netdev@vger.kernel.org, netdev-owner@vger.kernel.org
Subject: Re: restoring IP multicast addresses when restarting the interface.
Date: Tue, 24 Apr 2012 14:28:33 -0700	[thread overview]
Message-ID: <OFB8B0B17A.86602877-ON882579EA.00741868-882579EA.0075F72B@us.ibm.com> (raw)
In-Reply-To: <20120424.170004.1811627706738841106.davem@davemloft.net>

netdev-owner@vger.kernel.org wrote on 04/24/2012 02:00:04 PM:

> From: David Miller <davem@davemloft.net>

> >> I don't see why they should disappear when the interface goes
> >> down and then comes back up since these ultimately come from
> >> application sockets which continue to exist after a down/up.
> > 
> > Yeah, but that's not how things used to work before, so my
> > question is if the kernel should be responsible for keeping
> > the subscription or the application.
> > 
> > If the admin puts down the interface and remove the module,
> > for instance, then the multicast subscription is gone.
> > Should the application monitor for that then?
> > 
> > David? Any thoughts?
> 
> David Stevens at IBM and Herbert at the current multicast
> experts, so I will defer to them.

I think restoring the hardware multicast filter on device up
is useful, desirable and not a bug. :-)

                                                +-DLS

  reply	other threads:[~2012-04-24 21:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-21  0:25 restoring IP multicast addresses when restarting the interface Flavio Leitner
2012-04-23 12:14 ` Herbert Xu
2012-04-24 18:30   ` Flavio Leitner
2012-04-24 21:00     ` David Miller
2012-04-24 21:28       ` David Stevens [this message]
2012-04-24 22:19         ` Flavio Leitner

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=OFB8B0B17A.86602877-ON882579EA.00741868-882579EA.0075F72B@us.ibm.com \
    --to=dlstevens@us.ibm.com \
    --cc=davem@davemloft.net \
    --cc=fbl@redhat.com \
    --cc=herbert@gondor.hengli.com.au \
    --cc=netdev-owner@vger.kernel.org \
    --cc=netdev@vger.kernel.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 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.