[ovs-dev] [PATCH monitor_cond V3 01/10] ovsdb: create column index mapping between ovsdb row to monitor row

[Liran Schour]

Andy Zhou <azhou at 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.