[
https://issues.apache.org/jira/browse/DISPATCH-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16784916#comment-16784916
]
ASF subversion and git services commented on DISPATCH-1274:
-----------------------------------------------------------
Commit 077710c72a20f854e9fe0cbcd983ba68c4d72d10 in qpid-dispatch's branch
refs/heads/master from Alan Conway
[ https://gitbox.apache.org/repos/asf?p=qpid-dispatch.git;h=077710c ]
DISPATCH-1274: Separate qd_timer_t lock from server
qd_timer_t was sharing a lock with qd_server_t for historical reasons.
Code inspection shows there is no need for the sharing.
- timer.c calls qd_server_timeout() which is thread-safe, and no other server
functions.
- timer calls handlers outside the lock so it doesn't mater what lock is used.
> Optimize qd_timer_schedule(0)
> ------------------------------
>
> Key: DISPATCH-1274
> URL: https://issues.apache.org/jira/browse/DISPATCH-1274
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Container
> Affects Versions: 1.5.0
> Reporter: Alan Conway
> Assignee: Alan Conway
> Priority: Major
>
> qd_timer_schedule() uses the general timeout mechanisms which includes
> checking system time (on schedule and on PN_PROACTOR_TIMEOUT wakeup) and
> adding/removing work items from sorted list. Optimize the schedule(0) case as
> a simple work_list using pn_proactor_interrupt() for wakeups.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
