Review Board 1.7.16


Convert ast_channel over to astobj2

Review Request #203 - Created March 19, 2009 and submitted

Russell Bryant
/trunk
Reviewers
asterisk-dev
Asterisk
This patch converts handling of the ast_channel data structure over to the astobj2 framework.  There is a lot that could be said about this, but the patch is a bit improvement for performance, stability, code maintainability, and ease of future code development.

The channel list is no longer an unsorted linked list.  The main container for channels is an astobj2 hash table.  All of the code related to searching for channels or iterating active channels has been rewritten.  Let n be the number of active channels.  Iterating the channel list has gone from O(n^2) to O(n).  Searching for a channel by name went from O(n) to O(1).  Searching for a channel by extension is still O(n), but uses a new method for doing so, which is more efficient.

The ast_channel object is now a reference counted object.  The benefits here are plentiful.  Some benefits directly related to issues in the previous code include:

1) When threads other than the channel thread owning a channel wanted access to a channel, it had to hold the lock on it to ensure that it didn't go away.  This is no longer a requirement.  Holding a reference is sufficient.

2) There are places that now require less dealing with channel locks.

3) There are places where channel locks are held for much shorter periods of time.

4) There are places where dealing with more than one channel at a time becomes _MUCH_ easier.  ChanSpy is a great example of this.  Writing code in the future that deals with multiple channels will be much easier.

Some additional information regarding channel locking and reference count handling can be found in channel.h, where a new section has been added that discusses some of the rules associated with it.

Mark Michelson also assisted with the development of this patch.  He did the conversion of ChanSpy and introduced a new API, ast_autochan, which makes it much easier to deal with holding on to a channel pointer for an extended period of time and having it get automatically updated if the channel gets masqueraded.

Thanks to David Vossel for his assistance with this branch, as well.  David did the converstion of the DAHDIScan application by making it become a wrapper for ChanSpy internally.
I've done some basic testing making calls, transfers, etc., and I know Mark has done some, too.  However, this is one of those patches that seems like you can never test it enough.

Basically, any usage of Asterisk is useful testing for this.
/trunk/CHANGES
Revision 189986 New Change
[20] 25 lines
[+20]
26
 * Added progress option to the app_dial D() option.  When progress DTMF is
26
 * Added progress option to the app_dial D() option.  When progress DTMF is
27
   present, those values are sent immediatly upon receiving a PROGRESS message
27
   present, those values are sent immediatly upon receiving a PROGRESS message
28
   regardless if the call has been answered or not.
28
   regardless if the call has been answered or not.
29
 * Added functionality to the app_dial F() option to continue with execution
29
 * Added functionality to the app_dial F() option to continue with execution
30
   at the current location when no parameters are provided.
30
   at the current location when no parameters are provided.

    
   
31
 * Added c() option to app_chanspy. This option allows custom DTMF to be set

    
   
32
   to cycle through the next avaliable channel.  By default this is still '*'.

    
   
33
 * Added x() option to app_chanspy.  This option allows DTMF to be set to

    
   
34
   exit the application.
31

    
   
35

   
32
Dialplan Functions
36
Dialplan Functions
33
------------------
37
------------------
34
 * Added new dialplan functions CONNECTEDLINE and REDIRECTING which permits
38
 * Added new dialplan functions CONNECTEDLINE and REDIRECTING which permits
35
   setting various connected line and redirecting party information.
39
   setting various connected line and redirecting party information.
[+20] [20] 1136 lines
/trunk/UPGRADE.txt
Revision 189986 New Change
 
/trunk/apps/app_channelredirect.c
Revision 189986 New Change
 
/trunk/apps/app_chanspy.c
Revision 189986 New Change
 
/trunk/apps/app_dahdiscan.c
Revision 189986 New Change
 
/trunk/apps/app_directed_pickup.c
Revision 189986 New Change
 
/trunk/apps/app_minivm.c
Revision 189986 New Change
 
/trunk/apps/app_mixmonitor.c
Revision 189986 New Change
 
/trunk/apps/app_senddtmf.c
Revision 189986 New Change
 
/trunk/apps/app_softhangup.c
Revision 189986 New Change
 
/trunk/apps/app_voicemail.c
Revision 189986 New Change
 
/trunk/build_tools/cflags.xml
Revision 189986 New Change
 
/trunk/channels/chan_agent.c
Revision 189986 New Change
 
/trunk/channels/chan_bridge.c
Revision 189986 New Change
 
/trunk/channels/chan_dahdi.c
Revision 189986 New Change
 
/trunk/channels/chan_gtalk.c
Revision 189986 New Change
 
/trunk/channels/chan_iax2.c
Revision 189986 New Change
 
/trunk/channels/chan_local.c
Revision 189986 New Change
 
/trunk/channels/chan_mgcp.c
Revision 189986 New Change
 
/trunk/channels/chan_misdn.c
Revision 189986 New Change
 
  1. /trunk/CHANGES: Loading...
  2. /trunk/UPGRADE.txt: Loading...
  3. /trunk/apps/app_channelredirect.c: Loading...
  4. /trunk/apps/app_chanspy.c: Loading...
  5. /trunk/apps/app_dahdiscan.c: Loading...
  6. /trunk/apps/app_directed_pickup.c: Loading...
  7. /trunk/apps/app_minivm.c: Loading...
  8. /trunk/apps/app_mixmonitor.c: Loading...
  9. /trunk/apps/app_senddtmf.c: Loading...
  10. /trunk/apps/app_softhangup.c: Loading...
  11. /trunk/apps/app_voicemail.c: Loading...
  12. /trunk/build_tools/cflags.xml: Loading...
  13. /trunk/channels/chan_agent.c: Loading...
  14. /trunk/channels/chan_bridge.c: Loading...
  15. /trunk/channels/chan_dahdi.c: Loading...
  16. /trunk/channels/chan_gtalk.c: Loading...
  17. /trunk/channels/chan_iax2.c: Loading...
  18. /trunk/channels/chan_local.c: Loading...
  19. /trunk/channels/chan_mgcp.c: Loading...
  20. /trunk/channels/chan_misdn.c: Loading...
This diff has been split across 2 pages: 1 2 >

https://reviewboard.asterisk.org/ runs on a server provided by Digium, Inc. and uses bandwidth donated to the open source Asterisk community by API Digital Communications in Huntsville, AL USA.
Please report problems with this site to asteriskteam@digium.com.