[
https://issues.apache.org/jira/browse/PROTON-2250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17155664#comment-17155664
]
ASF subversion and git services commented on PROTON-2250:
---------------------------------------------------------
Commit 181c213166d27f5e371400feb65da7d50ebf2b03 in qpid-proton's branch
refs/heads/master from Andrew Stitcher
[ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=181c213 ]
PROTON-2250: Rearrange epoll locks to avoid locking in one place and unlocking
in another
> Simplify the locking inside the proactor epoll implementation
> -------------------------------------------------------------
>
> Key: PROTON-2250
> URL: https://issues.apache.org/jira/browse/PROTON-2250
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-c
> Reporter: Andrew Stitcher
> Assignee: Andrew Stitcher
> Priority: Major
> Fix For: proton-c-0.32.0
>
>
> There is significant complexity in the proactor epoll locking - to the extent
> that it is (or at least I find it) hard to reason about where locks are taken
> and release.
> Some of this complexity is due to the locks not being strictly hierarchical
> and some of them are taken in one place and then released in another.
> There may be a performance justification for this complexity, but I would
> like to simplify the locking and then improve it if it is found to be a real
> performance issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
