OVS commit 1cc618c32524 ("ovsdb-idl: Fix atomicity of writes that
don't change a column's value.") [0] explains why writes that don't
change a column's value cannot be optimized out early if the column is
read/write.
In northd, most tables have change tracking enabled, making all their
columns rea
On 3/29/22 11:40, Dumitru Ceara wrote:
> OVS commit 1cc618c32524 ("ovsdb-idl: Fix atomicity of writes that
> don't change a column's value.") [0] explains why writes that don't
> change a column's value cannot be optimized out early if the column is
> read/write.
>
> In northd, most tables have ch
On 4/1/22 13:28, Dumitru Ceara wrote:
> On 3/29/22 11:40, Dumitru Ceara wrote:
>> OVS commit 1cc618c32524 ("ovsdb-idl: Fix atomicity of writes that
>> don't change a column's value.") [0] explains why writes that don't
>> change a column's value cannot be optimized out early if the column is
>> rea
