No subject
Tue Feb 11 0:13:18 2003
Return-Path: xorp-cvs-admin@icir.org
Delivery-Date: Tue, 11 Feb 2003 00:14:03 -0800
Received: from wyvern.icir.org (wyvern.icir.org [192.150.187.14])
by tigger.icir.org (8.12.3/8.12.3) with ESMTP id h1B8E3ws023830
for <atanu@tigger.icir.org>; Tue, 11 Feb 2003 00:14:03 -0800 (PST)
(envelope-from xorp-cvs-admin@icir.org)
Received: from ICSI.Berkeley.EDU (fruitcake.ICSI.Berkeley.EDU [192.150.186.11])
by wyvern.icir.org (8.12.3/8.12.3) with ESMTP id h1B8E260037926
for <atanu@icir.org>; Tue, 11 Feb 2003 00:14:02 -0800 (PST)
(envelope-from xorp-cvs-admin@icir.org)
Received: from fruitcake.icsi.Berkeley.EDU (localhost [127.0.0.1])
by ICSI.Berkeley.EDU (8.9.0/8.9.0) with ESMTP id AAA25859;
Tue, 11 Feb 2003 00:14:02 -0800 (PST)
Received: from wyvern.icir.org (wyvern.icir.org [192.150.187.14])
by ICSI.Berkeley.EDU (8.9.0/8.9.0) with ESMTP id AAA25834
for <xorp-cvs@icsi.berkeley.edu>; Tue, 11 Feb 2003 00:13:19 -0800 (PST)
Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68])
by wyvern.icir.org (8.12.3/8.12.3) with ESMTP id h1B8DI60037924
for <xorp-cvs@icir.org>; Tue, 11 Feb 2003 00:13:18 -0800 (PST)
(envelope-from pavlin@xorpc.icir.org)
Received: from xorpc.icir.org (localhost [127.0.0.1])
by xorpc.icir.org (8.12.3/8.12.3) with ESMTP id h1B8DI8a080516
for <xorp-cvs@icir.org>; Tue, 11 Feb 2003 00:13:18 -0800 (PST)
(envelope-from pavlin@xorpc.icir.org)
Received: (from pavlin@localhost)
by xorpc.icir.org (8.12.3/8.12.3/Submit) id h1B8DIAU080515;
Tue, 11 Feb 2003 00:13:18 -0800 (PST)
(envelope-from pavlin)
From: Pavlin Radoslavov <pavlin@icir.org>
Message-Id: <200302110813.h1B8DIAU080515@xorpc.icir.org>
Date: Tue, 11 Feb 2003 0:13:18 ()
To: xorp-cvs@icir.org
Reply-To: pavlin@icir.org
Subject: [Xorp-cvs] XORP cvs commit: xorp/pim/ pim_mre.hh pim_mre_assert.cc pim_mre_track_state.cc
Sender: xorp-cvs-admin@icir.org
Errors-To: xorp-cvs-admin@icir.org
X-BeenThere: xorp-cvs@icir.org
X-Mailman-Version: 2.0
Precedence: bulk
List-Help: <mailto:xorp-cvs-request@icir.org?subject=help>
List-Post: <mailto:xorp-cvs@icir.org>
List-Subscribe: <http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-cvs>,
<mailto:xorp-cvs-request@icir.org?subject=subscribe>
List-Id: Mailing list for XORP CVS commit messages <xorp-cvs.icir.org>
List-Unsubscribe: <http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-cvs>,
<mailto:xorp-cvs-request@icir.org?subject=unsubscribe>
CVSROOT: /usr/local/share/doc/apache/cvs
Module name: xorp
Repository: xorp/pim/
Changes by: pavlin@xorpc.icir.org. 03/02/11 00:13:18
Modified files:
xorp/pim/: pim_mre.hh pim_mre_assert.cc pim_mre_track_state.cc
Log message:
Change the mechanism to recompute
CouldAssert(S,G,I), CouldAssert(*,G,I),
AssertTrackingDesired(S,G,I), and AssertTrackingDesired(*,G,I):
Originally, PimMre::recompute_assert_tracking_desired_sg(vif_index)
and friends were applied per interface, and that interface
was the one that had triggered the recomputation (e.g., because
a Join/Prune, etc message was received on that interface).
However, in case of events such as receiving winning Assert message,
Join/Prune, etc on an interface, this may change the
AssertTrackingDesired(S,G,I) state of the RPF_interface(S) or
RPF_interface(RP(G)); i.e., the state of an interface that is
different from the one that had triggered the recomputation.
The solution is whenever there is a single event that may affect
the AssertTrackingDesired(S,G,I) state for any interface, then
recompute AssertTrackingDesired(S,G,I) for all interfaces in
parallel, and apply the appropriate actions only for those
interfaces whose state has changed.
_______________________________________________
Xorp-cvs mailing list
Xorp-cvs@icir.org
http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-cvs