{"push_id":1361629412,"size":1,"distinct_size":1,"ref":"refs/heads/bus5","head":"2020048b0810a94f44898a9dd1a9f3e489e92e72","before":"4d4f6e2ac4ad73a82e851083c19ba688c86b631a","commits":[{"sha":"2020048b0810a94f44898a9dd1a9f3e489e92e72","author":{"name":"Nischal Sheth","email":"f3695c088f74f048a0592581cf8bf2e2bfb73369@juniper.net"},"message":"Make BgpSenderPartition::UpdatePeerQueue more efficient\n\nThe old implementation used to go through all peers for a RibOut\nand build a bitset of send ready peers to pass to PeerDequeue.\nThe bitset is used to decide which peers to merge with the start\nmarker when we encounter other markers while doing peer dequeue.\n\nThe new implementation determines which peers are send ready more\ndynamically i.e. as we encounter other markers during peer dequeue.\nThis avoids unnecessary work in cases where we do not encounter\nmany markers.  This could be because some markers are behind the\nstart marker for the peer or because the all peers in the start\nmarker get blocked or because some peers are in the tail marker.\nFurther, the new implementation determines the send ready state\ndirectly from the RibOut instead of the BgpUpdateSender since the\nRibOut state is more authoritative.\n\nAlso treat send_ready state in PeerState as advisory and send_ready\nin the IPeerUpdate as authoritative. This if justified because the\nIPeerUpdate could become blocked while processing updates from some\nother BgpSenderPartition.\n\nAlso fix a few update related UTs appropriately.\n\nChange-Id: Ib40d0a0d71c48f56e1af30962cc6f2459be4140a\nPartial-Bug: 1607132","distinct":true,"url":"https://api.github.com/repos/nischalsheth/contrail-controller/commits/2020048b0810a94f44898a9dd1a9f3e489e92e72"}]}
{"actor":{"display_login":"nischalsheth"}}