Re: [PATCH v3 0/4] cgroup notifications API and memory thresholds

[Kirill A. Shutemov]

On Sat, Dec 26, 2009 at 3:30 PM, Balbir Singh <balbir@xxxxxxxxxxxxxxxxxx> wrote:
> * Kirill A. Shutemov <kirill@xxxxxxxxxxxxx> [2009-12-26 02:30:56]:
>
>> This patchset introduces eventfd-based API for notifications in cgroups and
>> implements memory notifications on top of it.
>>
>> It uses statistics in memory controler to track memory usage.
>>
>> Output of time(1) on building kernel on tmpfs:
>>
>> Root cgroup before changes:
>> Â Â Â make -j2 Â506.37 user 60.93s system 193% cpu 4:52.77 total
>> Non-root cgroup before changes:
>> Â Â Â make -j2 Â507.14 user 62.66s system 193% cpu 4:54.74 total
>> Root cgroup after changes (0 thresholds):
>> Â Â Â make -j2 Â507.13 user 62.20s system 193% cpu 4:53.55 total
>> Non-root cgroup after changes (0 thresholds):
>> Â Â Â make -j2 Â507.70 user 64.20s system 193% cpu 4:55.70 total
>> Root cgroup after changes (1 thresholds, never crossed):
>> Â Â Â make -j2 Â506.97 user 62.20s system 193% cpu 4:53.90 total
>> Non-root cgroup after changes (1 thresholds, never crossed):
>> Â Â Â make -j2 Â507.55 user 64.08s system 193% cpu 4:55.63 total
>>
>> Any comments?
>
> Could you please add some documentation for end users.

Sure. I'll send new version of patchset with documentation soon.

> I've just
> compiled a kernel with your changes for test. Also, is there a reason
> not to use cgroupstats?

I'm not sure that understand you correctly. Could you explain the idea?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/