aboutsummaryrefslogtreecommitdiffstats
path: root/host/lib/rfnoc/client_zero.cpp
diff options
context:
space:
mode:
authorMartin Braun <martin.braun@ettus.com>2019-08-01 16:05:06 -0700
committerMartin Braun <martin.braun@ettus.com>2019-11-26 11:49:36 -0800
commitbddaac5e2678b190719228fc26877af5a2ef1910 (patch)
treec8e092f84e09ecd5e678c829294973068a7da292 /host/lib/rfnoc/client_zero.cpp
parent35db8f741b4b6c0bccf04e68e81bc4ecb5018357 (diff)
downloaduhd-bddaac5e2678b190719228fc26877af5a2ef1910.tar.gz
uhd-bddaac5e2678b190719228fc26877af5a2ef1910.tar.bz2
uhd-bddaac5e2678b190719228fc26877af5a2ef1910.zip
rfnoc: graph: Optimize property propagation algorithm
This introduces the concept of a resolution context, because the property propagation algorithm needs to behave differently when called during an initialization step (e.g. when the graph is committed), or when the user changes a property on one of the nodes after it was committed. The algorithm is modified as follows: - When called during an initialization step, then all nodes get resolved at least once. If nodes added new properties, then all nodes get touched again until the max number of iterations is reached. - When called because a node modified one of its properties, then that node is always resolved first. From there, all other nodes are resolved in topological order. However, the algorithm immediately terminates as soon as there are no more dirty nodes. - When called because a node modified one of its properties, but the graph is currently not in a committed state, then that node will do a local property resolution.
Diffstat (limited to 'host/lib/rfnoc/client_zero.cpp')
0 files changed, 0 insertions, 0 deletions