[
https://issues.apache.org/jira/browse/PROTON-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271537#comment-17271537
]
ASF subversion and git services commented on PROTON-2328:
---------------------------------------------------------
Commit b4ce6127df4e9be84ebc5a6a98750bf4feb403ad in qpid-proton's branch
refs/heads/master from Clifford Jansen
[ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=b4ce612 ]
PROTON-2328: epoll proactor, use local variable not zeroed task member to track
warm pairings
> epoll proactor bug in tracking previous task used by a thread
> -------------------------------------------------------------
>
> Key: PROTON-2328
> URL: https://issues.apache.org/jira/browse/PROTON-2328
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Affects Versions: proton-c-0.33.0
> Environment: linux
> Reporter: Clifford Jansen
> Assignee: Clifford Jansen
> Priority: Major
> Fix For: proton-c-0.34.0
>
>
> If an unassigned (ready) task and a free thread were each most recently
> working together, the epoll proactor tries to reassign them together for the
> next processing of the task, so that a warm memory cache may help performance.
> One half of this pairing information is in tslot_t->prev_task. This value is
> always set to NULL, defeating the warm cache strategy. In unassign_thread()
> prev_task should be set from the local variable that contains the correct
> value and not the member variable tslot_t->task which is zeroed on an earlier
> line.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
