Ondrej Zajicek 42eb4a1972 Nest: Fix several issues with pflags ... There were some confusion about validity and usage of pflags, which caused incorrect usage after some flags from (now removed) protocol- specific area were moved to pflags. We state that pflags: - Are secondary data used by protocol-specific hooks - Can be changed on an existing route (in contrast to copy-on-write for primary data) - Are irrelevant for propagation (not propagated when changed) - Are specific to a routing table (not propagated by pipe) The patch did these fixes: - Do not compare pflags in rte_same(), as they may keep cached values like BGP_REF_STALE, causing spurious propagation. - Initialize pflags to zero in rte_get_temp(), avoid initialization in protocol code, fixing at least two forgotten initializations (krt and one case in babel). - Improve documentation about pflags		2024-05-30 12:29:59 +02:00
..
config.Y	Perf: allow testing with cached route attributes.	2019-10-09 17:47:14 +02:00
Doc	Perf: Protocol to measure BIRD performance internally	2018-12-18 15:08:31 +01:00
Makefile	Simplified the protocol hookup code in Makefiles	2022-08-18 22:07:30 +02:00
parse.pl	Perf: Protocol to measure BIRD performance internally	2018-12-18 15:08:31 +01:00
perf.c	Nest: Fix several issues with pflags	2024-05-30 12:29:59 +02:00
perf.h	Perf: changed route update pattern to be more like common protocols	2020-03-12 09:26:05 +01:00