[ovs-dev] [PATCH] ovsdb-idl: Add additional support for change tracking.

Russell Bryant rbryant at redhat.com
Fri Aug 21 18:01:06 UTC 2015


On 08/21/2015 01:30 PM, Ansari, Shad wrote:
> Ovsdb-idl notifies a client that something changed; it does not track
> which table, row changed in what way (insert, modify or delete).
> As a result, a client has to scan or reconfigure the entire idl after
> ovsdb_idl_run(). This is presumably fine for typical ovs schemas where
> tables are relatively small. In use-cases where ovsdb is used with schemas
> that can have very large tables, the current ovsdb-idl notification
> mechanism does not appear to scale - clients need to do a lot of
> processing to determine the exact change delta.
> 
> This change adds support for:
> - Table and row based change sequence numbers to record the
>    most recent IDL change sequence numbers associated with insert,
>    modify or delete update on that table or row.
> - Allow change tracking of specific columns. This ensures that changed
>    rows (inserted, modified, deleted) that have tracked columns, are
>    tracked by IDL. The client can directly access the changed rows
>    with get_first, get_next operations without the need to scan the
>    entire table.
>    The tracking functionality is not enabled by default and needs to
>    be turned on per-column by the client after ovsdb_idl_create()
>    and before ovsdb_idl_run().
> 
> Signed-off-by: Shad Ansari shad.ansari at hp.com<mailto:shad.ansari at hp.com>

It looks like something messed up your signed-off-by header.

I haven't reviewed the patch yet but wanted to say thanks for looking
into this!  This sounds really useful for OVN.

-- 
Russell Bryant



More information about the dev mailing list