You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Niklas Quarfot Nielsen (JIRA)" <ji...@apache.org> on 2014/11/17 20:45:33 UTC

[jira] [Resolved] (MESOS-1912) Decouple libev from clock implementation

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

Niklas Quarfot Nielsen resolved MESOS-1912.
-------------------------------------------
    Resolution: Fixed

commit 0e19796dec8db07e2a60df15b88970dc387fbe21
Author: Benjamin Hindman <be...@gmail.com>
Date:   Sun Nov 2 17:04:25 2014 -0800

    Moved Clock implementation into clock.cpp.

    Review: https://reviews.apache.org/r/27503

> Decouple libev from clock implementation
> ----------------------------------------
>
>                 Key: MESOS-1912
>                 URL: https://issues.apache.org/jira/browse/MESOS-1912
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Niklas Quarfot Nielsen
>            Assignee: Benjamin Hindman
>
> In context of replacing libev with libevent, we need to decouple the current clock implementation from the event system (libev).
> The current clock implementation is implemented and entangled in process.cpp with dependencies on the global event loop and synchronized access to run queue and timers. The refactor is a matter of isolating those dependencies and make the event system call trigger clock ticks in Clock.



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