[pjsip] memory usage of epoll implementation

Benny Prijono bennylp at pjsip.org
Mon Aug 18 07:47:57 EDT 2008


On Mon, Aug 18, 2008 at 10:09 AM, Simon Chen <simonmychen at seed.net.tw>wrote:

>  Hi!
>
>     In ioqueue_select.c, memory of pj_ioqueue_key_t will be reused when
> compiler option "PJ_IOQUEUE_HAS_SAFE_UNREG" is set. But in
> ioqueue_epoll.c, it doesn't support this.
>
>     In pj_ioqueue_register_sock(), it allocates the memory and creates a
> mutex for pj_ioqueue_key_t by pj_pool_zalloc. But these memory will not be
> released before memory poll is released. This will increase the memory
> usage after calling pj_ioqueue_register_sock() in ioqueue_epoll.c. Can
> ioqueue_epoll.c add the same mechanism to avoid the memory increase? Is
> there any other concern? Thanks!
>
>

In general, the epoll ioqueue backend is not actively maintained lately,
hence it's not even offered as configuration choice. So I'm not surprised
that it has some holes in it. If you think you can make it work, feel free
to suggest a patch, I'd be happy to review it. :)

Cheers
 Benny



> Simon Chen
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20080818/9dbc03b3/attachment-0001.html 


More information about the pjsip mailing list