You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (Updated) (JIRA)" <ji...@apache.org> on 2011/10/05 00:40:36 UTC

[jira] [Updated] (TS-54) UnixNet cleanup, encapsulation of event subsystem

     [ https://issues.apache.org/jira/browse/TS-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom updated TS-54:
----------------------------

    Fix Version/s:     (was: 3.1.2)
                   3.2.0
    
> UnixNet cleanup, encapsulation of event subsystem
> -------------------------------------------------
>
>                 Key: TS-54
>                 URL: https://issues.apache.org/jira/browse/TS-54
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Cleanup
>         Environment: all unixesque
>            Reporter: John Plevyak
>            Assignee: John Plevyak
>             Fix For: 3.2.0
>
>         Attachments: proposed-jp-v1-List.h, ts-List-net-cleanup-jp-v2.patch, ts-List_and_net-cleanup-jp-v1.patch
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> The UnixNet subsystem was modified for epoll, but lots of the old data structures, data members and code
> remain for the old "bucket" approach.
> The epoll code should also be encapsulated to simplify support for other platforms and a possible move
> to an event library.
> The current code is complicated by limitations in Queue which require specifying the link field for every
> use, but which can be fixed by in the template.
> Finally, the current code does an unnecessary allocation for the epoll struct which should be part of the NetVConnection etc.
> and it takes a lock for the enable_queue which can be avoided by using the non-locking AtomicSSL.
> This work is also good preparation for evaluating libev or libevent as it will reduce the amount of code which
> will have to be changed.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira