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 (JIRA)" <ji...@apache.org> on 2014/05/23 18:45:02 UTC

[jira] [Commented] (TS-1835) Eliminate ink_resource.{cc,h}

    [ https://issues.apache.org/jira/browse/TS-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007345#comment-14007345 ] 

Leif Hedstrom commented on TS-1835:
-----------------------------------

[~bcall] I might have done a booboo here in the past. I think these files were accidentally over-cleaned up ... Can you check with the old YTS code, and perhaps see if you can put back the stuff that implements the Resource lookups etc. ?

I'm going to move this out to v5.1.0 though, we can look at it together later?

> Eliminate ink_resource.{cc,h}
> -----------------------------
>
>                 Key: TS-1835
>                 URL: https://issues.apache.org/jira/browse/TS-1835
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Core
>            Reporter: Leif Hedstrom
>            Assignee: Leif Hedstrom
>             Fix For: 5.0.0
>
>
> I think we should eliminate the ink_resource memory tracking code. We already have support for this when linking in with tcmalloc or jemalloc, rolling our own seems pointless with these tools being available.



--
This message was sent by Atlassian JIRA
(v6.2#6252)