TED update - 13: optimizing TE-Link link-reservation entries

#Optimized #TE-Link #link-reservation entries in TED module. The #reservation #priority has been added to the link-reservation entries, so that #preemption feature can be optimally implemented for #path #computation procedures. The #link-reservation #index has been made #compact by removing the 4 integer indexes and #replaced them with a #generic 16 byte #wide #index. This helps to keep traffic-engineering module to be less specific to the MPLS framework, as the generic index can be used from other modules as well. Also this makes link-reservation database more easily usable. The #preemption is used for #high #priority #path #setup #requests in the #traffic-engineering module. Preemption is used when #resource #crunch is experienced on a TE-Link for these requests. The #previously placed #low #priority resource #reservations will reused for performing current high priority request. The existing low priority reservations of will be either #teared #down or #moved to a different TE-Link. The bandwidth that got available from handling the low priority reservations will be used for current high priority path setup request.

#TED update 13 ...
[commit dcc8fa6c7a1eeddf3954da8671719bdb4ed62d25] (https://github.com/nes-repo/NES-Open-Switch/commit/dcc8fa6c7a1eeddf3954da8671719bdb4ed62d25)

TED update - 8: adding TE-Link reservation database

#Added #TE-Link #reservation parameters agent routines in TED module. On #LSP #reservation on the TE-Link an entry is made to keep #track of the #reservation just made. These entries hold the #bandwidth information related to each LSP reservation. On creating a #in-segment over a #mpls-interface, a reservation is done over the respective TE-Link and #link-reservation entry is created. On events like #protection #switching or an #LSP #tear #down the respective link-reservation entries will be appropriately handled. This stands as a #database of all the #reservations done in the system for various services LSPs. This allows to avoid complex cases as #double #reservations, where #backup or #detour #paths are involved. The #bandwidth consumed by each reservation is marked in the #link-reservation entries and when #make-before-break ( #MBB ) use-cases are involved it helps to get current #reservation and make #changes accordingly.

#TED update 8 ...
[commit 9bea6e0c39a5d80ccab1a8244a677f65955a1ee8] (https://github.com/nes-repo/NES-Open-Switch/commit/9bea6e0c39a5d80ccab1a8244a677f65955a1ee8)