[test-results] [Bamboo] Asterisk Testing > Asterisk Trunk > #18 was SUCCESSFUL (with 206 tests). Change made by rmudgett.

[Bamboo]

-----------------------------------------------------------------------
Asterisk Testing > Asterisk Trunk > #18 was successful.
-----------------------------------------------------------------------
Code has been updated by rmudgett.
206 tests in total.

http://bamboo.asterisk.org/browse/TESTING-ASTERISKTRUNK-18/


--------------
Code Changes
--------------
rmudgett (357272):

>Astobj2 locking enhancement.
>
>Add the ability to specify what kind of locking an ao2 object has when it
>is allocated.  The locking could be one of: MUTEX, RWLOCK, or none.
>
>New API:
>
>ao2_t_alloc_options()
>ao2_alloc_options()
>ao2_t_container_alloc_options()
>ao2_container_alloc_options()
>
>ao2_rdlock()
>ao2_wrlock()
>ao2_tryrdlock()
>ao2_trywrlock()
>
>The OBJ_NOLOCK and AO2_ITERATOR_DONTLOCK flags have a slight meaning
>change.  They no longer mean that the object is protected by an external
>mechanism.  They mean the lock associated with the object has already been
>manually obtained by one of the ao2_lock calls.  This change is necessary
>for RWLOCK support since they are not reentrant.  Also an operation on an
>ao2 container may require promoting a read lock to a write lock by
>releasing the already held read lock to re-acquire as a write lock.
>
>
>Replaced API calls:
>
>ao2_t_link_nolock()
>ao2_link_nolock()
>ao2_t_unlink_nolock()
>ao2_unlink_nolock()
>
>with the respective
>
>ao2_t_link_flags()
>ao2_link_flags()
>ao2_t_unlink_flags()
>ao2_unlink_flags()
>
>API calls to be more flexible and to allow an anticipated enhancement to
>control linking duplicate objects into a container.
>
>
>The changes to format.c and format_cap.c are taking advantange of the new
>ao2 locking options to simplify the use of the format capabilities
>containers.
>
>Review: https://reviewboard.asterisk.org/r/1554/
>


--
This message is automatically generated by Atlassian Bamboo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/test-results/attachments/20120228/fdb2e8e2/attachment-0001.htm>