Hi all, The documentation for odp_schedule_order_lock(unsigned lock_index) does not specify the sequence in which the lock_index need to be given.
Shouldn't the following statements be included in description of this function? 1) All code paths calling this function (in the same synchronization context) need to use the same lock_index sequence, eg: 1, 3, 2, 4 or the results are undefined (like the sequence of events will not be preserved) if this rule is not followed 2) The doc should emphasize a bit more to what the synchronization context is bound to (source queue). For eg. it should say that lock_index sequence can be different for different source queues (synchronization contexts). 3) It is possible to skip some lock_index in sequence. But skipped lock_indexes cannot be used outside of the sequence (since this will alter the sequence which is violation of rule 1).
