On Thu, Apr 6, 2017 at 8:22 AM, Radosław Biernacki wrote:
> Hi Bill,
>
> Thank you for reply and sorry for my long reply.
>
> IMHO the description which you give could be copied to
> doc/users-guide/users-guide.adoc as there are not many information how this
> should work across all implementation
Hi Bill,
Thank you for reply and sorry for my long reply.
IMHO the description which you give could be copied to
doc/users-guide/users-guide.adoc as there are not many information how this
should work across all implementations.
I don't fully understand following sentence "since each individual i
On Wed, Mar 29, 2017 at 7:18 AM, Radosław Biernacki wrote:
> 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.
That's because there is no such required sequence. Each lock index is
a distinct or
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
c
