Project

General

Profile

Actions
Copy link

Task #2864

closed

A RoutingTable calculation should only update NamePrefixTableEntries with an affected RoutingTableEntry

Added by Vince Lehman over 9 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Nicholas Gordon
Target version:
v0.4.0
Start date:
Due date:
% Done:

0%

Estimated time:

Description

Currently, NamePrefixTable::updateWithNewRoute() updates all the RoutingTableEntries for each NamePrefixTableEntry even if the RoutingTableEntry was not changed by the RoutingTable calculation.

Instead, NamePrefixTable::updateWithNewRoute() should only modify the NamePrefixTableEntry's RoutingTableEntries when they contain a RoutingTableEntry affected by the calculation.

Related issues 3 (0 open — 3 closed)

Blocked by NLSR - Task #2862: Create flowchart for interaction between RoutingTable, NamePrefixTable, and FIBClosedMuktadir Chowdhury06/09/2015

Actions
Blocked by NLSR - Task #2863: NamePrefixTableEntries should store RoutingTableEntries using a pointerClosedNicholas Gordon06/09/2015

Actions
Blocks NLSR - Task #4249: Make NamePrefixTable and RoutingTable communicate through signalsClosedNicholas Gordon

Actions
Actions
Copy link
 #1

Updated by Vince Lehman over 9 years ago

  • Blocked by Task #2862: Create flowchart for interaction between RoutingTable, NamePrefixTable, and FIB added
Actions
Copy link
 #2

Updated by Vince Lehman over 9 years ago

  • Target version set to v0.3.0
Actions
Copy link
 #3

Updated by Nicholas Gordon over 8 years ago

  • Target version changed from v0.3.0 to v0.3.1
Actions
Copy link
 #4

Updated by Nicholas Gordon over 8 years ago

  • Blocked by Task #2863: NamePrefixTableEntries should store RoutingTableEntries using a pointer added
Actions
Copy link
 #5

Updated by Nicholas Gordon over 7 years ago

  • Target version deleted (v0.3.1)
Actions
Copy link
 #6

Updated by Nicholas Gordon over 7 years ago

  • Target version set to v0.5.0

Because this is only an optimization and not of high urgency, this is going to v0.5.0. Additionally, because the currently-used topologies are not large, even full-refresh is not extremely costly.

Actions
Copy link
 #7

Updated by Nicholas Gordon over 7 years ago

  • Blocks Task #4249: Make NamePrefixTable and RoutingTable communicate through signals added
Actions
Copy link
 #8

Updated by Nicholas Gordon over 7 years ago

  • Status changed from New to Code review
  • Assignee set to Nicholas Gordon
  • Target version changed from v0.5.0 to v0.4.0
  • Start date deleted (06/09/2015)
Actions
Copy link
 #9

Updated by Nicholas Gordon about 7 years ago

  • Has duplicate Task #4249: Make NamePrefixTable and RoutingTable communicate through signals added
Actions
Copy link
 #10

Updated by Nicholas Gordon about 7 years ago

  • Has duplicate deleted (Task #4249: Make NamePrefixTable and RoutingTable communicate through signals)
Actions
Copy link
 #11

Updated by Nicholas Gordon about 7 years ago

Worth noting that the NPT no longer uses plain RoutingTableEntries, as issue #2863 has been implemented and closed. As such, this issue refers to the local copies of those entries that the NPT now keeps.

Actions
Copy link
 #12

Updated by Nicholas Gordon about 7 years ago

  • Status changed from Code review to Closed
Actions
Copy link

Also available in: Atom PDF