Vincent - You are correct that better meeting minutes would be helpful. I run the meetings and don't have time to write notes as I go, so we get stuff cobbled together at the end. To answer your original question about the why of it: 1) We have several known situations where show commands for bgp take an extraordinary amount of time to run/process( especially with JSON output turned on ). This long time is causing bgp neighbor relationships to be taken down because hello's are not getting out. 2) Quentin/David/Olivier have all been working/thinking about threads and all have slightly different approaches. This last round of changes changed an api that was found to be surprising after it was committed. At that point we decided that it would be a good idea to spend a couple hours( or more ) hammering out the general approach we want to take. Hence this meeting donald On Thu, May 18, 2017 at 9:37 AM, Vincent Jardin <vincent.jardin@6wind.com> wrote:
Maybe some minutes for people who could not attend would help ? This topic related to thread needs to on board many view.
Le 18 mai 2017 2:18:01 PM Donald Sharp <sharpd@cumulusnetworks.com> a écrit :
I thought we already agree'd on the rational in the weekly meetings. This meetings purpose is to nail down the approach we want to take because we keep having discussions about the long term approach, which means we need to nail it down.
donald
On Thu, May 18, 2017 at 8:04 AM, Vincent Jardin <vincent.jardin@6wind.com> wrote:
David,
It seems I did miss the Doodle. First, please, we need a written rational of Quentin's intention when he did push pthread support.
Le 18 mai 2017 1:38:55 PM David Lamparter <equinox@opensourcerouting.org> a écrit :
Hi all,
as polled on Doodle (and with Lou's side-input), the Multithreading design call mentioned in our last weekly meeting will be
tomorrow (Friday) 08:00 PDT (US West Coast -0700) 11:00 EDT (US East Coast -0400) 17:00 CEST (EU Central +0200)
I'll also send out calendar invites.
Cheers,
-David
_______________________________________________ dev mailing list dev@lists.frrouting.org https://lists.frrouting.org/listinfo/dev
_______________________________________________ dev mailing list dev@lists.frrouting.org https://lists.frrouting.org/listinfo/dev