lib/ovsdb-idl.c
/* Returns a "sequence number" that represents the state of 'idl'.  When
 * ovsdb_idl_run() changes the database, the sequence number changes.  The
 * initial fetch of the entire contents of the remote database is considered to
 * be one kind of change.  Successfully acquiring a lock, if one has been
 * configured with ovsdb_idl_set_lock(), is also considered to be a change.
 *
 * As long as the sequence number does not change, the client may continue to
 * use any data structures it obtains from 'idl'.  But when it changes, the
 * client must not access any of these data structures again, because they
 * could have freed or reused for other purposes.
 *
 * The sequence number can occasionally change even if the database does not.
 * This happens if the connection to the database drops and reconnects, which
 * causes the database contents to be reloaded even if they didn't change.  (It
 * could also happen if the database server sends out a "change" that reflects
 * what the IDL already thought was in the database.  The database server is
 * not supposed to do that, but bugs could in theory cause it to do so.) */
Returns a "sequence number" that represents the state of 'idl'.  When
ovsdb_idl_run() changes the database, the sequence number changes.  The
initial fetch of the entire contents of the remote database is considered to
be one kind of change.  Successfully acquiring a lock, if one has been
configured with ovsdb_idl_set_lock(), is also considered to be a change.

As long as the sequence number does not change, the client may continue to
use any data structures it obtains from 'idl'.  But when it changes, the
client must not access any of these data structures again, because they
could have freed or reused for other purposes.

The sequence number can occasionally change even if the database does not.
This happens if the connection to the database drops and reconnects, which
causes the database contents to be reloaded even if they didn't change.  (It
could also happen if the database server sends out a "change" that reflects
what the IDL already thought was in the database.  The database server is
not supposed to do that, but bugs could in theory cause it to do so.)
Returns a " sequence number " that represents the state of ' idl ' . When ovsdb_idl_run () changes the database the sequence number changes . The initial fetch of the entire contents of the remote database is considered to be one kind of change . Successfully acquiring a lock if one has been configured with ovsdb_idl_set_lock () is also considered to be a change . As long as the sequence number does not change the client may continue to use any data structures it obtains from ' idl ' . But when it changes the client must not access any of these data structures again because they could have freed or reused for other purposes . The sequence number can occasionally change even if the database does not . This happens if the connection to the database drops and reconnects which causes the database contents to be reloaded even if they didn ' t change . ( It could also happen if the database server sends out a " change " that reflects what the IDL already thought was in the database . The database server is not supposed to do that but bugs could in theory cause it to do so . )
unsigned int
ovsdb_idl_get_seqno(const struct ovsdb_idl *idl)
{
    return idl->data.change_seqno;
}
unsigned int ovsdb_idl_get_seqno ( const struct ovsdb_idl * idl ) { return idl -> data . change_seqno ; }
Returns a "sequence number" that represents the state of 'idl'.
Returns a " sequence number " that represents the state of ' idl ' .