On Sat, Feb 6, 2016 at 8:30 AM, Liran Schour <lir...@il.ibm.com> wrote:
> Andy Zhou <az...@ovn.org> wrote on 04/02/2016 08:29:32 PM: > > > > > in ovs sandbox, I started two monitor-cond sessions: > > > > 1: ovsdb-client monitor-cond '[["name", "!=", "xx"]]' Interface > ifindex > > 2: ovsdb-client monitor-cond '[["ifindex", "!=", 99]]' Interface name > > > > I'd think that both sessions should be able share a single monitor, > > but found that there are separate monitors for each session. > > Is this intentional? > > It is intentional and it does not related to this patch. > Sessions will share ovsdb_monitor only if they are monitoring the same > table set and columns in each table. This is essential for the JSON cache > to work. Look at ovsdb_monitor_equal() in monitor.c. > This patch does not breaks this restriction. > Thanks for clarifying. This is really a design question before I had a chance to read through the V3 in detail. Some how I had a different impression from the V2 review discussion and thought this test should have produced a shared dbmon, but found v3's implementation to be different. Now that I have reviewed V3 in detail, I understand the design better now. > > _______________________________________________ > dev mailing list > dev@openvswitch.org > http://openvswitch.org/mailman/listinfo/dev > _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
