You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Timothy Chen (JIRA)" <ji...@apache.org> on 2015/07/15 03:01:04 UTC

[jira] [Commented] (MESOS-2961) Add cpuacct subsystem utils to cgroups

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

Timothy Chen commented on MESOS-2961:
-------------------------------------

commit 9a5eaca9e3ab7ac01ae5f884b32e8c570da4f799
Author: Jojy Varghese <jo...@mesosphere.io>
Date:   Tue Jul 14 17:10:03 2015 -0700

    Added cpuacct subsystem to cgroups.

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

> Add cpuacct subsystem utils to cgroups
> --------------------------------------
>
>                 Key: MESOS-2961
>                 URL: https://issues.apache.org/jira/browse/MESOS-2961
>             Project: Mesos
>          Issue Type: Task
>          Components: containerization, docker, isolation
>         Environment: linux
>            Reporter: Jojy Varghese
>            Assignee: Jojy Varghese
>              Labels: containerizer, isolation, mesosphere
>
> Current cgroups implementation does not have a cpuacct subsystem implementation. This subsystem reports important metrics like user and system CPU ticks spent by a process. "cgroups" namespace has subsystem specific utilities for "cpu", "memory" etc. It could use other subsystems specific utils (eg. cpuacct).
> In the future, we could also view cgroups as a mesos-subsystem with  features like event notifications.
> Although refactoring cgroups would be a different epic, listing the possible tasks:
>   -  Have hierarchies, subsystems abstracted to represent the domain 
>   - Create  "cgroups service"
>   -  "cgroups service" listen to update events from the OS on files like stats. This would be an interrupt based system(maybe use linux fsnotify)
>   - "cgroups service" services events to mesos (containers for example).



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