Re: bgpd async nexthop update loop

2019-06-19 Thread Sebastian Benoit
ok! Claudio Jeker(cje...@diehard.n-r-g.com) on 2019.06.17 23:08:37 +0200: > On Mon, Jun 17, 2019 at 10:20:57PM +0200, Sebastian Benoit wrote: > > Claudio Jeker(cje...@diehard.n-r-g.com) on 2019.06.17 21:34:30 +0200: > > > Hi, > > > > > > Now that the community rewrite is in here another diff to

Re: bgpd async nexthop update loop

2019-06-17 Thread Claudio Jeker
On Mon, Jun 17, 2019 at 10:20:57PM +0200, Sebastian Benoit wrote: > Claudio Jeker(cje...@diehard.n-r-g.com) on 2019.06.17 21:34:30 +0200: > > Hi, > > > > Now that the community rewrite is in here another diff to make bgpd more > > awesome. There was one loop left that did not run asynchronous

Re: bgpd async nexthop update loop

2019-06-17 Thread Sebastian Benoit
Claudio Jeker(cje...@diehard.n-r-g.com) on 2019.06.17 21:34:30 +0200: > Hi, > > Now that the community rewrite is in here another diff to make bgpd more > awesome. There was one loop left that did not run asynchronous compared to > the main event loop. This loop was in nexthop_update() now a

bgpd async nexthop update loop

2019-06-17 Thread Claudio Jeker
Hi, Now that the community rewrite is in here another diff to make bgpd more awesome. There was one loop left that did not run asynchronous compared to the main event loop. This loop was in nexthop_update() now a route server or a big route reflector would be hit hard by this loop since it will