You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafficserver.apache.org by "John Plevyak (JIRA)" <ji...@apache.org> on 2010/01/05 07:06:54 UTC
[jira] Created: (TS-102) AIO should callback on
AIO/calling/any_ethread thread instead of current AIO for write or any for
reads
AIO should callback on AIO/calling/any_ethread thread instead of current AIO for write or any for reads
-------------------------------------------------------------------------------------------------------
Key: TS-102
URL: https://issues.apache.org/jira/browse/TS-102
Project: Traffic Server
Issue Type: Improvement
Components: Cleanup
Reporter: John Plevyak
Assignee: John Plevyak
Priority: Minor
Fix For: 2.1.0
AIO currently is special cased to callback writes on the AIO thread and reads on
a random event thread. This is inflexible and a hidden part of the API and it makes
it difficult to ptimize thread switching in the cache. This solution is to expose this
in the AIO API.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TS-102) AIO should callback on
AIO/calling/any_ethread thread instead of current AIO for write or any for
reads
Posted by "John Plevyak (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TS-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Plevyak closed TS-102.
---------------------------
Resolution: Fixed
Committed revision 896234
> AIO should callback on AIO/calling/any_ethread thread instead of current AIO for write or any for reads
> -------------------------------------------------------------------------------------------------------
>
> Key: TS-102
> URL: https://issues.apache.org/jira/browse/TS-102
> Project: Traffic Server
> Issue Type: Improvement
> Components: Cleanup
> Reporter: John Plevyak
> Assignee: John Plevyak
> Priority: Minor
> Fix For: 2.1.0
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> AIO currently is special cased to callback writes on the AIO thread and reads on
> a random event thread. This is inflexible and a hidden part of the API and it makes
> it difficult to ptimize thread switching in the cache. This solution is to expose this
> in the AIO API.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.