You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Alan M. Carroll (JIRA)" <ji...@apache.org> on 2015/12/16 03:34:46 UTC

[jira] [Updated] (TS-1775) Cleanup of ink_hrtime.{cc,h}

     [ https://issues.apache.org/jira/browse/TS-1775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alan M. Carroll updated TS-1775:
--------------------------------
    Fix Version/s:     (was: 6.1.0)
                   6.2.0

> Cleanup of ink_hrtime.{cc,h}
> ----------------------------
>
>                 Key: TS-1775
>                 URL: https://issues.apache.org/jira/browse/TS-1775
>             Project: Traffic Server
>          Issue Type: Improvement
>            Reporter: Leif Hedstrom
>            Assignee: Alan M. Carroll
>              Labels: newbie
>             Fix For: 6.2.0
>
>
> A few things comes to mind:
> 1) Why do we have a NEED_HRTIME define? It's always on as far as I can tell, and I can't imagine there's a reason to not have it on (it'd completely break like everything, in fact it would fail to compile since gethrtime() doesn't exist?).
> 2) We should eliminate the USE_TIME_STAMP_COUNTER_HRTIME define, and the code that implements our own TSC code. Modern Unix flavors implements this already in various way (e.g. glibc's gettimeofday() wrapper has a TSC user space implementation).
> 3) On FreeBSD, jpeach points out that CLOCK_REALTIME is probably not the optimal way to use clock_gettime(). He suggest using CLOCK_REALTIME_FAST or CLOCK_MONOTONIC_FAST which is similar to the optimizations done with TSC for gettimeofday() on linux.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)