[ovs-discuss] OVSDB server multi-threading

2016-07-07 Thread Ansari, Shad
Hi, I am trying to follow the OVSDB multi-threading patch discussed back in March (http://openvswitch.org/pipermail/dev/2016-March/067130.html). Appears this did not make it in. Anyone know the reasons why? -shad ___ discuss mailing list discuss@open

[ovs-discuss] FW: Scaling ovsdb-idl's update notification

2015-10-07 Thread Ansari, Shad
, 2015 9:08 PM > To: Ansari, Shad > Cc: Saurabh Shrivastava (सौरभ श्रीवास्तव); discuss@openvswitch.org > Subject: Re: [ovs-discuss] Scaling ovsdb-idl's update notification > > If that's useful for real applications, and more practical, then I'm all > for it. I h

Re: [ovs-discuss] Scaling ovsdb-idl's update notification

2015-08-03 Thread Ansari, Shad
. Typically, the uuid or indexes should be sufficient information for the client to take action. -Original Message- From: Ben Pfaff [mailto:b...@nicira.com] Sent: Monday, August 03, 2015 9:51 AM To: Saurabh Shrivastava (सौरभ श्रीवास्तव) Cc: Ansari, Shad; discuss@openvswitch.org Subject: Re

[ovs-discuss] Scaling ovsdb-idl's update notification

2015-07-31 Thread Ansari, Shad
Ovsdb-idl notifies a client that "something" changed; it does not track "what" changed. The client then typically either reconfigures itself by scanning the idl to determine what changed, or - simply reloads the entire idl. This presumably works since the ovs schema tables aren't typically larg