Messages in this thread | | | From | Paul Menage <> | Date | Fri, 19 Nov 2010 12:38:09 -0800 | Subject | Re: [RFC/RFT PATCH v3] sched: automated per tty task groups |
| |
On Fri, Nov 19, 2010 at 11:12 AM, Ben Gamari <bgamari.foss@gmail.com> wrote: > On that note, is there a good reason why the notify_on_release interface > works the way it does? Wouldn't it be simpler if the cgroup simply > provided a file on which a process (e.g. systemd) could block?
Backwards-compatibility with cpusets, which is what cgroups evolved from.
A delete_on_release option would be possible too, for the cases where there's really no entity that wants to do more than simply delete the group in question.
Paul
| |