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

Timothy St. Clair commented on MESOS-996:
-----------------------------------------

Greeting Ian - 

I've yet to dig deeply into *this, but I plan to near term.  
I'm wondering if the code is structured to handle the new world order that is 
coming around systemd:
http://www.freedesktop.org/wiki/Software/systemd/ControlGroupInterface/



> Refactor linux/cgroups functions for separate subsystem mounts.
> ---------------------------------------------------------------
>
>                 Key: MESOS-996
>                 URL: https://issues.apache.org/jira/browse/MESOS-996
>             Project: Mesos
>          Issue Type: Improvement
>          Components: isolation
>    Affects Versions: 0.18.0
>            Reporter: Ian Downes
>            Priority: Minor
>
> 0.18.0 requires each cgroup subsystem to be mounted separately, e.g., a 
> container's cgroup would be:{cgroups_hierarchy}/cpu/{cgroups_root}/container1
> It would be much cleaner if the cgroups abstraction understood this and 
> generally worked with the 3-tuple (hierarchy, subsystem, cgroup) rather than 
> the existing tuple (hierarchy, cgroup).



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to