[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <OF980F8B87.D755A28E-ON882577AB.00779881-882577AB.0077F27A@us.ibm.com>
Date: Mon, 27 Sep 2010 14:50:01 -0700
From: David Stevens <dlstevens@...ibm.com>
To: Christoph Lameter <cl@...ux.com>
Cc: Jason Gunthorpe <jgunthorpe@...idianresearch.com>,
linux-rdma@...r.kernel.org, netdev@...r.kernel.org,
netdev-owner@...r.kernel.org, Bob Arendt <rda@...con.com>
Subject: Re:
Christoph Lameter <cl@...ux.com> wrote on 09/27/2010 01:23:00 PM:
> From: Christoph Lameter <cl@...ux.com>
> To: David Stevens/Beaverton/IBM@...US
> Cc: Jason Gunthorpe <jgunthorpe@...idianresearch.com>, linux-
> rdma@...r.kernel.org, netdev@...r.kernel.org, netdev-
> owner@...r.kernel.org, Bob Arendt <rda@...con.com>
> Date: 09/27/2010 01:23 PM
> Subject: Re:
>
> On Mon, 27 Sep 2010, David Stevens wrote:
>
> > Because a querier can set the robustness value and
> > query interval to anything you want. In the original report,
> > he's not running a querier. The fact that it's a new group
> > doesn't matter -- these are per-interface.
>
> The per interface settings are used to force an IGMP version overriding
> any information by the queriers.
No. I'm not talking about the force_igmp_tunable here, I'm talking
about the per-interface robustness and interval settings which come from
the querier (whatever version you are using).
> You would not want to enable that because
> it disables support for other IGMP versions. Without the override
> different version of IGMP can be handled per MC group.
No. IGMPv3 includes backward compatibility for both IGMPv2 and
IGMPv1. If queries for an earlier version are present, that is the
IGMP version all use, and the features of the later version are not
available to anyone.
+-DLS
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists